[ 
https://issues.apache.org/jira/browse/HBASE-10102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Hofhansl resolved HBASE-10102.
-----------------------------------

    Resolution: Won't Fix

[[email protected]] just pointed out that even if we fixed this issue, 
we'd have to remove time based HFile selection in order to find the count the 
newer values even when we're only interested in the older ones. Clearly a no go.
Closing as "Won't fix".

> CF.VERSIONS is not enforced with timerange scans
> ------------------------------------------------
>
>                 Key: HBASE-10102
>                 URL: https://issues.apache.org/jira/browse/HBASE-10102
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>         Attachments: 10102-0.94-POC.txt
>
>
> Example brought up by Niels Basjes on the user list:
> If I do the following commands into the hbase shell
> {code}
>     create 't1', {NAME => 'c1', VERSIONS => 1}
>     put 't1', 'r1', 'c1', 'One', 1000
>     put 't1', 'r1', 'c1', 'Two', 2000
>     put 't1', 'r1', 'c1', 'Three', 3000
>     get 't1', 'r1'
>     get 't1', 'r1' , {TIMERANGE => [0,1500]}
> the result is this:
>     get 't1', 'r1'
>     COLUMN                     CELL
>      c1:                       timestamp=3000, value=Three
>     1 row(s) in 0.0780 seconds
>     get 't1', 'r1' , {TIMERANGE => [0,1500]}
>     COLUMN                     CELL
>      c1:                       timestamp=1000, value=One
>     1 row(s) in 0.1390 seconds
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to