You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Slava (JIRA)" <ji...@apache.org> on 2008/11/28 22:38:44 UTC

[jira] Issue Comment Edited: (HBASE-1014) commit(BatchUpdate) method should return timestamp

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

slavag edited comment on HBASE-1014 at 11/28/08 1:38 PM:
--------------------------------------------------------

The question when to set a timestamp into BU when no immediate flush ? 
I think like in transactional case, where BU is not flushed immediately, the
timestamp is set during insertion of the BU into transactional log, same
could be in the case when BU is inserted into  cache. BTW, setting it in the
client will act exactly the same.


      was (Author: slavag):
    The question when to set a timestamp into BU when no immediate flush. I
think like in transactional case, where BU is not flushed immediately, the
timestamp is set during insertion of the BU into transactional log, same
could be in the case when BU is inserted into  cache. BTW, setting it in the
client will act exactly the same.

  
> commit(BatchUpdate)  method should return timestamp
> ---------------------------------------------------
>
>                 Key: HBASE-1014
>                 URL: https://issues.apache.org/jira/browse/HBASE-1014
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Slava
>             Fix For: 0.19.0
>
>
> The commit(BatchUpdate) and commit(list<BatchUpdate>) should return timestamp that BatchUpdate was committed with (in the case of commit(list<BatchUpdate> should return array of timestamps). 
> This should reduce number of round trips and improve performance in update operations.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.