[
https://issues.apache.org/jira/browse/HBASE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693606#action_12693606
]
Erik Holstad commented on HBASE-1249:
-------------------------------------
So what you gain by going with number 1 instead of number 2 is that you don't
need to check any of the storefiles for more than containment of a
DeleteFamily insert, so no need to check the timestamp for every get and for
merging of deletes, since yo know that all the deletes that are in that
storefile are inserted after the DeleteFamily insert was made. The only time
you actually take care of removing stuff in regards to the DeleteFamily call is
in memCache. So basically you dont' have to do the checks for the DeleteFamily
timestamp, because you know that none of the storefiles after the storefile
where you encountered the DeleteFamily entry are "deleted".
Regards Erik
> 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-Example-v1.pdf, HBASE-1249-Example-v2.pdf,
> HBASE-1249-GetQuery-v1.pdf, HBASE-1249-GetQuery-v2.pdf,
> HBASE-1249-GetQuery-v3.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.
