Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 27392 invoked from network); 20 Aug 2007 19:47:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Aug 2007 19:47:54 -0000 Received: (qmail 56611 invoked by uid 500); 20 Aug 2007 19:47:50 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 56584 invoked by uid 500); 20 Aug 2007 19:47:50 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 56575 invoked by uid 99); 20 Aug 2007 19:47:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Aug 2007 12:47:50 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Aug 2007 19:48:23 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 81F9D714213 for ; Mon, 20 Aug 2007 12:47:30 -0700 (PDT) Message-ID: <15980468.1187639250516.JavaMail.jira@brutus> Date: Mon, 20 Aug 2007 12:47:30 -0700 (PDT) From: "stack (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Updated: (HADOOP-1737) [hbase] Make HColumnDescriptor data publically members settable In-Reply-To: <1403979.1187539050685.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/HADOOP-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HADOOP-1737: -------------------------- Attachment: hadoop-1737.patch Here's a first attempt. HADOOP-1737 Make HColumnDescriptor data publically members settable M src/contrib/hbase/src/java/org/apache/hadoop/hbase/HStore.java Use new HColumnDescriptor accessors rather than make direct accesses M src/contrib/hbase/src/java/org/apache/hadoop/hbase/HColumnDescriptor.java (COMPRESSION_NONE, COMPRESSION_RECORD, COMPRESSION_BLOCK): Removed. Use enum ordinals instead. Removed mapping between these defines and enum equivalents. Made data members private and added accessors. (DEFAULT_IN_MEMORY, DEFAULT_COMPRESSION_TYPE, DEFAULT_BLOOM_FILTER_DESCRIPTOR, DEFAULT_MAX_VALUE_LENGTH): Added. > [hbase] Make HColumnDescriptor data publically members settable > ---------------------------------------------------------------- > > Key: HADOOP-1737 > URL: https://issues.apache.org/jira/browse/HADOOP-1737 > Project: Hadoop > Issue Type: Bug > Components: contrib/hbase > Reporter: stack > Assignee: stack > Priority: Minor > Attachments: hadoop-1737.patch > > > On the list Inchol Song made the following reasonable request: > Inchul Song wrote: > > I am making changes to Hbase Shell to add support for > > the new CREATE TABLE syntax. (See issue HADOOP-1720.) > > > > But there are only two useful constructors in class HColumnDescriptor > > for column creation, one with an argument specifying a column name, > > the other with a number of arguments specifying all the options > > for the column such as a compression method, max length, and so on, > > > > In a CREATE TABLE statement, when a user specifies only > > some of the available options, I'd like to fill in the remaining options > > with their default values. I expected to access those default values as > > public static fields of the HColumnDescriptor class, but those values > > were hidden in the class as private fields. So I had to look into > > the source code of the HColumnDescriptor class to find out > > which default values are used in its single argument constructor. > > > > I think it would be useful to make the default option values > > in the HColumnDescriptor class as public static fields. > > > > Is there any reason not to make them public static fields? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.