[
https://issues.apache.org/jira/browse/HBASE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Gray updated HBASE-1249:
---------------------------------
Attachment: HBASE-1249-GetQuery-v2.pdf
Erik pointed out that return codes 3 and 4 are not explicit about whether you
should include the current value or not in the ResultSet.
This updates the spec so that 3 and 4 mean DO NOT include the current key in
the result. This means that you
Also note, another optimization we will have is removing things in the Get that
are to be matched once we have matched all that are required. For example, we
specify we want the most recent versions of 5 explicit columns. Once we find
one of them, they will be removed from the match list. Once all are found, and
thus removed, the next compareTo call will see that there is nothing left to
match on and return a 4. Return code of 3 would be used in many other cases,
for example, if we're looking for all versions of a single column, once we scan
past that column in the current storefile, we return 3 to jump to the next one.
> 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
>
> Attachments: HBASE-1249-GetQuery-v1.pdf, HBASE-1249-GetQuery-v2.pdf,
> HBASE-1249-StoreFile-v1.pdf
>
>
> 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.
