[ 
https://issues.apache.org/jira/browse/HBASE-1249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12680633#action_12680633
 ] 

Jonathan Gray commented on HBASE-1249:
--------------------------------------

Comments on above:

1.  Not exactly following you, stack.  I think Erik's idea is that when we are 
doing any kind of get that is explicit with the columns, we can match any 
deletes we find against the input list of columns.  Just removing them from 
this list, rather than keeping a running list of deletes, should be more 
efficient.  This leads into a new discussion I will post on next.

2.  I'm +1 on Erik's thought.  Timestamps should not be set client side.  If 
there is a need to know the timestamp, might be possible to have it returned.  
But the ability to set the timestamp means we can never optimize when dealing 
with versions because there could be a newer version of something in an older 
storefile, thus no ability to early-out ever.  If you need more control over 
the timestamp, then you probably aren't really using versions for versioning 
and you should model your data differently.

3.  +1

Not really sure what the opinion is for family + qualifier.  I see no reason to 
store or use the : ever, anywhere.  Client APIs should separate family and 
column as separate args.  Is there a good argument for not doing it this way?  
Our comparators and new key format have no need for it.

> 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
>
>
> 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.

Reply via email to