Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@locus.apache.org Received: (qmail 36653 invoked from network); 12 Aug 2008 22:08:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Aug 2008 22:08:35 -0000 Received: (qmail 69723 invoked by uid 500); 12 Aug 2008 22:08:34 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 69708 invoked by uid 500); 12 Aug 2008 22:08:34 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 69697 invoked by uid 99); 12 Aug 2008 22:08:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Aug 2008 15:08:34 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Aug 2008 22:07:46 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 51248234C1AC for ; Tue, 12 Aug 2008 15:07:44 -0700 (PDT) Message-ID: <1517426903.1218578864331.JavaMail.jira@brutus> Date: Tue, 12 Aug 2008 15:07:44 -0700 (PDT) From: "stack (JIRA)" To: hbase-dev@hadoop.apache.org Subject: [jira] Commented: (HBASE-795) More Table operation in TableHandler for REST interface In-Reply-To: <1530179533.1217895044523.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622003#action_12622003 ] stack commented on HBASE-795: ----------------------------- This is a nice patch. Applies fine. I took it for a spin doing the prescription outlined above. All works nicely. Only issues I see is what if there exists already a table named 'tables' and the lack of documentation of REST in general (not your fault). Maybe you should rename the 'tables' switch to be a name you know is illegal as a legit tablename: e.g. _tables or some such (See HTableDescriptor.isLegalTableName for rules). Meantime, I'm going to apply this since it adds nice functionality. If you get a chance, add package doc. to REST, if only to point back at the wiki page, and fix the 'tables' issue if you come up w/ an idea better than mine above. > More Table operation in TableHandler for REST interface > ------------------------------------------------------- > > Key: HBASE-795 > URL: https://issues.apache.org/jira/browse/HBASE-795 > Project: Hadoop HBase > Issue Type: New Feature > Components: rest > Reporter: sishen.freecity > Attachments: 795.trunk.rest_table.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > In the current implementation, only the metadata query of table allowed. It's not convinent to use the REST interface to write a third-party client library. I think the functionality of REST interface should be similar with the hbase shell. So user can create/show/update/delate/enable/disable the table. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.