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

stack commented on HBASE-4256:
------------------------------

On 1. I think it depends.

addColumn can specify a (a) cf only, (b) a cf+qualifier, or a list of (c) 
cf+qualifiers.

If (a), then the setStartQualifier/setEndQualifier would return items from 
within a CF between the specified qualifiers (do you need an 
'inclusive/exclusive' flag or you just going to have them be both inclusive of 
specified qualifier?)

On (b), i'd think that we'd just return the qualifier only IFF it was within 
the setStartQualifier/setEndQualifier bounds.

For (c), we'd return members of the list that are inside the 
setStartQualifier/setEndQualifier bounds.

I think I prefer 2. api to 1. api.  It maps well to TimeRange.  Its a bit more 
of a pain specifying 'start x to the end of the row' with api 2. but its 
palatable enough.

Ditto on how api 2. plays with addColumn.
                
> Intra-row scanning (part deux)
> ------------------------------
>
>                 Key: HBASE-4256
>                 URL: https://issues.apache.org/jira/browse/HBASE-4256
>             Project: HBase
>          Issue Type: New Feature
>    Affects Versions: 0.90.4
>            Reporter: Jean-Daniel Cryans
>            Assignee: Dave Revell
>            Priority: Critical
>             Fix For: 0.94.0
>
>
> Dave Revell was asking on IRC today if there's a way to scan ranges of 
> *qualifiers* within a row. That is, to be able to specify a *start qualifier* 
> and an *end qualifier* so that the Get or Scan seeks directly to the first 
> qualifier and stops at some point which can be predeterminate by a qualifier 
> or simply a batch configuration (already exists).
> This is particularly useful for large rows with time-based qualifiers.
> Dave also mentioned that another popular database has such a feature that 
> they call "column slices".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to