hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phabricator (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5542) Unify HRegion.mutateRowsWithLocks() and HRegion.processRow()
Date Fri, 09 Mar 2012 21:00:58 GMT

    [ https://issues.apache.org/jira/browse/HBASE-5542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226451#comment-13226451
] 

Phabricator commented on HBASE-5542:
------------------------------------

lhofhansl has commented on the revision "HBASE-5542 [jira] Unify HRegion.mutateRowsWithLocks()
and HRegion.processRow()".

INLINE COMMENTS
  src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java:4362 Hmm... That means we're
now running the coprocessor post host after the region operation closed.
  It almost seems that the RowProcessor should have three phases:
  1. A pre phase (without locks and mvcc, but with the WALEdit). The prephase could abort
the operation
  2. the op itself
  3. a post operation (after locks are released, mvcc is rolled forward)

REVISION DETAIL
  https://reviews.facebook.net/D2217

BRANCH
  5542-new-file

                
> Unify HRegion.mutateRowsWithLocks() and HRegion.processRow()
> ------------------------------------------------------------
>
>                 Key: HBASE-5542
>                 URL: https://issues.apache.org/jira/browse/HBASE-5542
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Scott Chen
>            Assignee: Scott Chen
>             Fix For: 0.96.0
>
>         Attachments: HBASE-5542.D2217.1.patch, HBASE-5542.D2217.2.patch, HBASE-5542.D2217.3.patch
>
>
> mutateRowsWithLocks() does atomic mutations on multiple rows.
> processRow() does atomic read-modify-writes on a single row.
> It will be useful to generalize both and have a
> processRowsWithLocks() that does atomic read-modify-writes on multiple rows.
> This also helps reduce some redundancy in the codes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message