[
https://issues.apache.org/jira/browse/HBASE-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710453#action_12710453
]
Jonathan Gray commented on HBASE-1304:
--------------------------------------
My opinion is, if you care about what the stamps are, then you should set them
manually. We could certainly figure out a way for a Put to return a long, but
could be very tricky considering a single put could be built with a different
timestamp for each column.
And what you're saying about the deleting of latest put, Erik, I agree that
this is actually not a particularly common use case and it should be sufficient
to allow explicit deletion by stamp. Any time you are mucking with the
version-level, you must be aware of the version dimension (the timestamp).
Since many use cases do not involve versions, I don't want to pollute
everything else to allow for something like explicitly deleting LATEST but no
others before it.
> New client server implementation of how gets and puts are handled.
> -------------------------------------------------------------------
>
> Key: HBASE-1304
> URL: https://issues.apache.org/jira/browse/HBASE-1304
> Project: Hadoop HBase
> Issue Type: Improvement
> Affects Versions: 0.20.0
> Reporter: Erik Holstad
> Assignee: Jonathan Gray
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: HBASE-1304-ryan.patch, hbase-1304-v1.patch,
> HBASE-1304-v2.patch, HBASE-1304-v3.patch, HBASE-1304-v4.patch,
> HBASE-1304-v5.patch, HBASE-1304-v6.patch, HBASE-1304-v7.patch
>
>
> Creating an issue where the implementation of the new client and server will
> go. Leaving HBASE-1249 as a discussion forum and will put code and patches
> here.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
