hbase-dev mailing list archives

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

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

stack commented on HBASE-1014:
------------------------------

One thing I've been thinking is how we'd do the notion of LATEST_TIMESTAMP if timestamps are
set on the client?  Client will always swap out LATEST_TIMESTAMP for an explicit time.  How
do we know serverside when this timestamp is meant to be the 'latest' rather than an explicit
timestamp get.

> 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