Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 10 Feb 2014 21:43:24 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12689922.1390264346744.19422.1392068604876@arcas>
In-Reply-To: <JIRA.12689922.1390264346744@arcas>
References: <JIRA.12689922.1390264346744@arcas>
Subject: [jira] [Updated] (HBASE-10389) Add namespace help info in table
 related shell commands
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-10389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enis Soztutar updated HBASE-10389:
----------------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

I committed this to trunk and 0.98. Thanks Jerry for the patch. 
The patch does not apply cleanly to 0.96, if you supply a patch, I can commit it there as well. 

> Add namespace help info in table related shell commands
> -------------------------------------------------------
>
>                 Key: HBASE-10389
>                 URL: https://issues.apache.org/jira/browse/HBASE-10389
>             Project: HBase
>          Issue Type: Improvement
>          Components: shell
>    Affects Versions: 0.96.0, 0.96.1
>            Reporter: Jerry He
>            Assignee: Jerry He
>             Fix For: 0.98.1, 0.99.0
>
>         Attachments: HBASE-10389-trunk.patch
>
>
> Currently in the help info of table related shell command, we don't mention or give namespace as part of the table name.  
> For example, to create table:
> {code}
> hbase(main):001:0> help 'create'
> Creates a table. Pass a table name, and a set of column family
> specifications (at least one), and, optionally, table configuration.
> Column specification can be a simple string (name), or a dictionary
> (dictionaries are described below in main help output), necessarily
> including NAME attribute.
> Examples:
>   hbase> create 't1', {NAME => 'f1', VERSIONS => 5}
>   hbase> create 't1', {NAME => 'f1'}, {NAME => 'f2'}, {NAME => 'f3'}
>   hbase> # The above in shorthand would be the following:
>   hbase> create 't1', 'f1', 'f2', 'f3'
>   hbase> create 't1', {NAME => 'f1', VERSIONS => 1, TTL => 2592000, BLOCKCACHE => true}
>   hbase> create 't1', {NAME => 'f1', CONFIGURATION => {'hbase.hstore.blockingStoreFiles' => '10'}}
> Table configuration options can be put at the end.
> Examples:
>   hbase> create 't1', 'f1', SPLITS => ['10', '20', '30', '40']
>   hbase> create 't1', 'f1', SPLITS_FILE => 'splits.txt', OWNER => 'johndoe'
>   hbase> create 't1', {NAME => 'f1', VERSIONS => 5}, METADATA => { 'mykey' => 'myvalue' }
>   hbase> # Optionally pre-split the table into NUMREGIONS, using
>   hbase> # SPLITALGO ("HexStringSplit", "UniformSplit" or classname)
>   hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit'}
>   hbase> create 't1', 'f1', {NUMREGIONS => 15, SPLITALGO => 'HexStringSplit', CONFIGURATION => {'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'}}
> You can also keep around a reference to the created table:
>   hbase> t1 = create 't1', 'f1'
> Which gives you a reference to the table named 't1', on which you can then
> call methods.
> {code}
> We should document the usage of namespace in these commands.
> For example:
> #namespace=foo and table qualifier=bar
> create 'foo:bar', 'fam'
> #namespace=default and table qualifier=bar
> create 'bar', 'fam'


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)