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

Ramon Wang commented on HBASE-9218:
-----------------------------------

I had the same problem when i trying to execute a 'alter' command, here is the 
cmd:

alter 'SPLIT_TEST_BIG', {METHOD => 'table_att', 'SPLIT_POLICY' => 
'org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy'}

The split policy is not changed for table 'SPLIT_TEST_BIG', by digging the 
code, i found HTableDescriptor.getRegionSplitPolicyClassName in method 
HRegion.initializeRegionInternals always returns null.

The HBase i'm using is 0.94.6-cdh4.4.0.

> HBase shell does not allow to change/assign custom table-column families 
> attributes
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-9218
>                 URL: https://issues.apache.org/jira/browse/HBASE-9218
>             Project: HBase
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 0.94.6.1
>            Reporter: Vladimir Rodionov
>
> HBase shell. In 0.94.6.1 the attempt to assign/change custom table or CF 
> attribute does not throw any exception but has no affect. The same code works 
> fine in Java API (on HTableDescriptor or HColumnDescriptor)
> This is short shell session snippet:
> {code}
> hbase(main):009:0> disable 'T'
> 0 row(s) in 18.0730 seconds
> hbase(main):010:0> alter 'T', NAME => 'df', 'FAKE' => '10'
> Updating all regions with the new schema...
> 5/5 regions updated.
> Done.
> 0 row(s) in 2.2900 seconds
> hbase(main):011:0> enable 'T'
> 0 row(s) in 18.7140 seconds
> hbase(main):012:0> describe 'T'
> DESCRIPTION                                                                   
>                                          ENABLED
>  {NAME => 'T', FAMILIES => [{NAME => 'df', DATA_BLOCK_ENCODING => 'NONE', 
> BLOOMFILTER = true
>  > 'NONE', REPLICATION_SCOPE => '0', VERSIONS => '1', COMPRESSION => 'GZ', 
> MIN_VERSIONS => '0', TTL => '2147483647', K
>  EEP_DELETED_CELLS => 'false', BLOCKSIZE => '65536', IN_MEMORY => 'true', 
> ENCODE_ON_DISK => 'true', BLOCKCACHE => 'tru
>  e'}]}
> {code}
> As you can see, the new attribute 'FAKE' has not been added to column family 
> 'cf'.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to