You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/16 16:36:00 UTC
[jira] [Resolved] (HBASE-7924) thrift interface is inconsistently implemented on timestamp/range scan
[ https://issues.apache.org/jira/browse/HBASE-7924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Kyle Purtell resolved HBASE-7924.
----------------------------------------
Resolution: Won't Fix
> 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
> Priority: Major
>
> 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 was sent by Atlassian Jira
(v8.20.7#820007)