Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 12 Oct 2012 20:07:03 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <405653859.39409.1350072423670.JavaMail.jiratomcat@arcas>
In-Reply-To: <1532497810.137759.1348809307885.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HBASE-6894) Adding metadata to a table in the
 shell is both arcane and painful
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-6894:
------------------------------

On 3., see "help 'create'".

On 2., do what you think best.  I'd be fine w/ CONFIG (or DICTIONARY? or DICT) for the arbitrary kvs and explicit, predefined constants like MAX_FILESIZE being individually called out.

It'd be grand if we did not have to have TABLE_CONFIG to refer to the dictionary in HTableDescriptor and then CONFIG for referring to it in the column family; these are not well named.  If we can't have the same key for table arbitrary attributes and column family attributes, then I'd say lets at least name them better even if its not backward compatible.

I don't think this table attribute stuff has to be backward compatible.  I'd be surprised any one even knew it existed never mind using it.

Good on you Sergey.  Thanks for looking at this.
                
> Adding metadata to a table in the shell is both arcane and painful
> ------------------------------------------------------------------
>
>                 Key: HBASE-6894
>                 URL: https://issues.apache.org/jira/browse/HBASE-6894
>             Project: HBase
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 0.96.0
>            Reporter: stack
>              Labels: noob
>         Attachments: HBASE-6894.patch, HBASE-6894.patch
>
>
> In production we have hundreds of tables w/ whack names like 'aliaserv', 'ashish_bulk', 'age_gender_topics', etc.  It be grand if you could look in master UI and see stuff like owner, eng group responsible, miscellaneous description, etc.
> Now, HTD has support for this; each carries a dictionary.  Whats a PITA though is adding attributes to the dictionary.  Here is what seems to work on trunk (though I do not trust it is doing the right thing):
> {code}
> hbase> create 'SOME_TABLENAME', {NAME => 'd', VERSION => 1, COMPRESSION => 'LZO'}
> hbase> # Here is how I added metadata
> hbase> disable 'SOME_TABLENAME'
> hbase> alter 'SOME_TABLENAME', METHOD => 'table_att', OWNER => 'SOMEON', CONFIG => {'ENVIRONMENT' => 'BLAH BLAH', 'SIZING' => 'The size should be between 0-10K most of the time with new URLs coming in and getting removed as they are processed unless the pipeline has fallen behind', 'MISCELLANEOUS' => 'Holds the list of URLs waiting to be processed in the parked page detection analyzer in ingestion pipeline.'}
> ...
> describe...
> enable...
> {code}
> The above doesn't work in 0.94.  Complains about the CONFIG, the keyword we are using for the HTD dictionary.
> It works in 0.96 though I'd have to poke around some more to ensure it is doing the right thing.
> But this METHOD => 'table_att' stuff is really ugly.... can we fix it?
> And I can't add table attributes on table create seemingly.
> A little bit of thought and a bit of ruby could clean this all up.

--
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