[
https://issues.apache.org/jira/browse/HBASE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680603#action_12680603
]
stack commented on HBASE-1249:
------------------------------
Thanks for the review Erik.
On 1., I've been thinking something similar -- do it in actual return list.
Need to keep the delete around though in case we come across a deleted value
subsequently. Was thinking just before we let the thing out of the server,
we'd remove deletes --- or something like that.
On 2., thats a big change. We should put it up on list.... something like
remove timestamping till we do it right because meantime it only gives wrong
impression.
On 3., once we have server passing client Set of KVBBs, yes, we should do this
as convenience for the perverse bit-shifters
Yeah, the type has extra space. We should remember that as you point out.
Ok on the family/qualifier stuff; lets get it into the patch we commit.
> Rearchitecting of server, client, API, key format, etc for 0.20
> ---------------------------------------------------------------
>
> Key: HBASE-1249
> URL: https://issues.apache.org/jira/browse/HBASE-1249
> Project: Hadoop HBase
> Issue Type: Improvement
> Reporter: Jonathan Gray
> Priority: Blocker
> Fix For: 0.20.0
>
>
> To discuss all the new and potential issues coming out of the change in key
> format (HBASE-1234): zero-copy reads, client binary protocol, update of API
> (HBASE-880), server optimizations, etc...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
