Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1839805948.1221833684326.JavaMail.jira@brutus>
Date: Fri, 19 Sep 2008 07:14:44 -0700 (PDT)
From: "Tim Sell (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-889) The current Thrift API does not allow
 a new scanner to be created without supplying a column list unlike the
 other APIs.
In-Reply-To: <1638156883.1221771164328.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tim Sell commented on HBASE-889:
--------------------------------

actually I was reading the REST code (branch 0.2), opening a scanner, it checks if the columns are specified, and if not 

      // TODO: Need to put into the scanner all of the table's column
      // families.  TODO: Verify this returns all rows.  For now just fail.
      doMethodNotAllowed(response, "Unspecified columns parameter currently not supported!");

Are you sure the REST api allows it? Unless I'm looking at the wrong code.

The obvious way to do this is if it's null we get the columns list from the table.

> The current Thrift API does not allow a new scanner to be created without supplying a column list unlike the other APIs.
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-889
>                 URL: https://issues.apache.org/jira/browse/HBASE-889
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: thrift
>    Affects Versions: 0.2.0, 0.2.1
>            Reporter: Charlie Mason
>
> The current Thrift API does not allow a new scanner to be created without supplying a column list, unlike the REST api. I posted this on the HBase-Users mailing list. Others concurred that it appears to have been an oversight in the Thrift API. 
> Its quite significant as there is no easy work around, unless you already know which the column families names then list them all when you open the scanner.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.