hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Daniel Cryans (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1014) commit(BatchUpdate) method should return timestamp
Date Fri, 28 Nov 2008 14:53:44 GMT

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

Jean-Daniel Cryans commented on HBASE-1014:
-------------------------------------------

If clients are located in different timezones, then it is already a problem since an update
that you just did could be in that client's future. So IMO that we set it on the client or
not, having a client in a different timezone is always a problem. But setting it in the client
do solve the problem of returning the timestamps in a batched commit without immediate flush.

> 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.


Mime
View raw message