[
https://issues.apache.org/jira/browse/HBASE-4507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13118498#comment-13118498
]
stack commented on HBASE-4507:
------------------------------
bq. Do we really need to modify checkAndPut here?
checkAndPut as is has a hole in that an update that writes the same value will
go unnoticed.
bq. I think it's safer to have explicit sequence IDs for the META rows and use
the existing checkAndPut. Unless there's some reason that won't work, I don't
think it's necessary to change a core function for this?
So, each time we set a region location (hostname + port + startcode), we'd also
update a new column, say info:editid, which would have a uuid value. We'd then
do checkAndPut on the info:editid column?
We'd still need to read whatever this value was at start of region open.
I could work up a patch for this over in hbase-4497 if its preferred.
Regards atomicMutation, that would be a nice improvement. Would deprecate
current APIs in favor of it going forward. Lets open a new issue to do that.
> Create checkAndPut variant that exposes timestamp / UUID
> --------------------------------------------------------
>
> Key: HBASE-4507
> URL: https://issues.apache.org/jira/browse/HBASE-4507
> Project: HBase
> Issue Type: Sub-task
> Reporter: Ted Yu
> Assignee: stack
>
> Michael checked the checkAndPut which doesn't expose timestamp. A variant of
> checkAndPut should be created to expose timestamp which is written into a
> column specified by additional parameters.
--
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
