Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C933CEB0C for ; Mon, 25 Feb 2013 10:04:14 +0000 (UTC) Received: (qmail 81384 invoked by uid 500); 25 Feb 2013 10:04:13 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 80937 invoked by uid 500); 25 Feb 2013 10:04:13 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 80609 invoked by uid 99); 25 Feb 2013 10:04:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Feb 2013 10:04:12 +0000 Date: Mon, 25 Feb 2013 10:04:12 +0000 (UTC) From: "Guido Serra aka Zeph (JIRA)" To: dev@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-7924) thrift interface is inconsistently implemented on timestamp/range filtering MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Guido Serra aka Zeph created HBASE-7924: ------------------------------------------- Summary: thrift interface is inconsistently implemented on timestamp/range filtering Key: HBASE-7924 URL: https://issues.apache.org/jira/browse/HBASE-7924 Project: HBase Issue Type: Bug Components: Thrift Affects Versions: 0.94.5, 0.92.0 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 instead, the Scan object is behaving as by documentation but the getRowsWithColumnsTs() beneath has a timerange behaviour see: HBASE-5694, HBASE-7907 -- 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