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

Lars Hofhansl commented on HBASE-4256:
--------------------------------------

What about the other points? Are we seeing this as:
1. A way to scan subset of many rows (would be inefficient as we need to reseek 
at the beginning of every new row)?
or
2. A scan strictly within a single row? (should enforce start/endRow set to the 
same value in this case.)
or
3. More control where to start and stop a scan? (leave the scan logic mostly 
the way it is, and allow a way to seek to a column of a row, and end at a 
different column in another row).

#1 makes no sense (to me anyway, but maybe there's something I didn't see).
#3 is a superset of #2. As described above, in this case we could start at 
RowX:QualA and scan to RowY:QualB, all rows between RowX and RowY would scan 
all Quals. Can be combined easily with timerange scans.

I'd be in favor of #3. Or #2 if it turns out to be less work.

                
> 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