[
https://issues.apache.org/jira/browse/HBASE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703506#action_12703506
]
Erik Holstad commented on HBASE-1249:
-------------------------------------
On the sorting of the types, that is good. So we have "bigger" deletes sorted
before smaller, so that they we be encountered first.
When I talked about deleteFamily being stored in a separate place that is when
you are doing a get call, not how they are stored in
the file. In the file they are stored first in the row, since they have an
empty value in the column field.
When it comes to deletes and timestamps the deleteFamily and deleteColumn
deletes all data that comes after that ts but for
delete it only deletes the given ts and does not affect other data.
In memcache if putting first a delete(ts1) and then after a while putting a
deleteColumn(ts3) the delete(ts1) is removed and deleteColumn(ts3) kept. But if
they are put in, in opposite order deleteColumn(ts1) and then delete(ts3) both
of them are kept.
Another optimization that is made in memcache and also can be done when doing a
minor compaction is to remove the delete itself in the case you find that exact
timestamp, only for delete and not for the "bigger" deletes.
> 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-GetQuery-v4.pdf,
> HBASE-1249-StoreFile-v1.pdf, HBASE-1249-StoreFile-v4.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.
