[
https://issues.apache.org/jira/browse/HBASE-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-1014:
-------------------------
Fix Version/s: 0.19.0
I'm w/ j-d on this one; set timestamp in client. I can't think of any
downside, only upside. Timestamp currently is set serverside by doing this
inside in HRegion#batchUpdate:
long commitTime = (b.getTimestamp() == LATEST_TIMESTAMP) ?
System.currentTimeMillis() : b.getTimestamp();
Bringing this issue into 0.19.0. Small change. Big payoff.
> 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.
