You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by liushaohui <li...@xiaomi.com> on 2013/05/03 14:48:56 UTC

HBASE-7570 is reverted by the commit of HBASE-7571

hi all,

    From the svn log,  I found that HBASE-7570 has been reverted by the 
commit of HBASE-7571.

HBASE-7570 renamed 'CONFIG' to 'METADATA' for per-CF/per-table 
configuration in hbase shell, but the name of this configuration is 
'CONFIG' in trunk.

Is there any reason?  What's the final name for per-CF/per-table 
configuration? thx


- liushaohui@xiaomi

Re: HBASE-7570 is reverted by the commit of HBASE-7571

Posted by Sergey Shelukhin <se...@hortonworks.com>.

Actually, it doesn't seem to be the case. Can you point out where you see
this?

On Fri, May 3, 2013 at 10:21 AM, Sergey Shelukhin <se...@hortonworks.com>wrote:

> Hmm, if this is indeed so it must be a mistake, these JIRAs were separate
> from a single patch in HBASE-7236 and were supposed to work together. Let
> me fix it
>
>
> On Fri, May 3, 2013 at 5:48 AM, liushaohui <li...@xiaomi.com> wrote:
>
>> hi all,
>>
>>    From the svn log,  I found that HBASE-7570 has been reverted by the
>> commit of HBASE-7571.
>>
>> HBASE-7570 renamed 'CONFIG' to 'METADATA' for per-CF/per-table
>> configuration in hbase shell, but the name of this configuration is
>> 'CONFIG' in trunk.
>>
>> Is there any reason?  What's the final name for per-CF/per-table
>> configuration? thx
>>
>>
>> - liushaohui@xiaomi
>>
>>
>>
>

Re: HBASE-7570 is reverted by the commit of HBASE-7571

Posted by Sergey Shelukhin <se...@hortonworks.com>.

Hmm, if this is indeed so it must be a mistake, these JIRAs were separate
from a single patch in HBASE-7236 and were supposed to work together. Let
me fix it

On Fri, May 3, 2013 at 5:48 AM, liushaohui <li...@xiaomi.com> wrote:

> hi all,
>
>    From the svn log,  I found that HBASE-7570 has been reverted by the
> commit of HBASE-7571.
>
> HBASE-7570 renamed 'CONFIG' to 'METADATA' for per-CF/per-table
> configuration in hbase shell, but the name of this configuration is
> 'CONFIG' in trunk.
>
> Is there any reason?  What's the final name for per-CF/per-table
> configuration? thx
>
>
> - liushaohui@xiaomi
>
>
>