[
https://issues.apache.org/jira/browse/HBASE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683403#action_12683403
]
ryan rawson commented on HBASE-1249:
------------------------------------
A few things:
- in the storefile pdf, you have a row like so:
RowA, Delete, Fam, ColA, 6, X
Is the 'X' a typo? This should be a */no value since deletes dont actually
carry any _value_ info - the info is in the key itself.
And as for the delete/memcache thing.... It sounds like we lose the ability to
version deletes if the value is in memcache. Eg:
- insert row A, ColA, value X
- delete row A, Col A
in a row, both will hit the memcache (probably). It seems like with your
proposal we would process the delete by nuking the insert (aka put) right away,
and storing the delete for posterity and to cover up older values in older
hfiles.
or am i missing something?
> 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-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.
