[
https://issues.apache.org/jira/browse/HBASE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703500#action_12703500
]
stack commented on HBASE-1249:
------------------------------
So v4 of doc. is wrong where it says Puts come before Deletes (thats fine).
Ok on the DeleteRow.
Sort from TRUNK KV is:
{code}
/**
* Key type.
* Has space for other key types to be added later. Cannot rely on
* enum ordinals . They change if item is removed or moved. Do our own codes.
*/
public static enum Type {
Put((byte)4),
Delete((byte)8),
DeleteColumn((byte)16),
DeleteFamily((byte)32),
// Maximum is used when searching; you look from maximum on down.
Maximum((byte)255);
{code}
I don't follow what you mean by "separate place" for DeleteFamily. That sounds
odd.
What about how deletes and timestamps mix? Does a delete only delete cell of
that ts? Or does it delete that ts and all behind?
> 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.
