stack created HBASE-6894:
----------------------------

             Summary: Adding metadata to HTableDescriptor is painful
                 Key: HBASE-6894
                 URL: https://issues.apache.org/jira/browse/HBASE-6894
             Project: HBase
          Issue Type: Bug
          Components: shell
    Affects Versions: 0.94.1
            Reporter: stack


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

Reply via email to