[ https://issues.apache.org/jira/browse/HBASE-7924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guido Serra aka Zeph updated HBASE-7924: ---------------------------------------- Description: a getRowsWithColumnsTs or a Scan object are being exposed (as by documentation and .thrift description file) only as *exact* timestamp matcher, no timerange functionality is (supposedly) being exposed -> see: HBASE-7907 instead, the Scan object is behaving as by documentation but the getRowsWithColumnsTs() beneath has a timerange behaviour {code} if (tScan.isSetTimestamp()) { scan.setTimeRange(Long.MIN_VALUE, tScan.getTimestamp()); } {code} see: HBASE-5694 was: a getRowsWithColumnsTs or a Scan object are being exposed (as by documentation and .thrift description file) only as *exact* timestamp matcher, no timerange functionality is (supposedly) being exposed instead, the Scan object is behaving as by documentation but the getRowsWithColumnsTs() beneath has a timerange behaviour {code} if (tScan.isSetTimestamp()) { scan.setTimeRange(Long.MIN_VALUE, tScan.getTimestamp()); } {code} see: HBASE-5694, HBASE-7907 > thrift interface is inconsistently implemented on timestamp/range scan > ---------------------------------------------------------------------- > > Key: HBASE-7924 > URL: https://issues.apache.org/jira/browse/HBASE-7924 > Project: HBase > Issue Type: Bug > Components: Thrift > Affects Versions: 0.92.0, 0.94.5 > Reporter: Guido Serra aka Zeph > > a getRowsWithColumnsTs or a Scan object are being exposed (as by > documentation and .thrift description file) only as *exact* timestamp matcher, > no timerange functionality is (supposedly) being exposed -> see: HBASE-7907 > instead, the Scan object is behaving as by documentation > but the getRowsWithColumnsTs() beneath has a timerange behaviour > {code} > if (tScan.isSetTimestamp()) { > scan.setTimeRange(Long.MIN_VALUE, tScan.getTimestamp()); > } > {code} > see: HBASE-5694 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira