[
https://issues.apache.org/jira/browse/HBASE-19340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16278283#comment-16278283
]
zhaoyuan edited comment on HBASE-19340 at 12/5/17 9:52 AM:
-----------------------------------------------------------
Hi [~chia7712] Please help me to review this patch If it is convenient for you.
I learned from HBASE-17736 and I found you have already add configuration
such as split_policy and flush_policy in admin.create() method. I think maybe
we should add the same logic in admin.alter() method or I missed the code .
Hope to hear from you.Thanks.
was (Author: smartzy):
Hi [~chia7712] Please help me to review this patch If it is convenient for you.
I learned from HBASE-17736(sorry I don't know how to add an issue link
quickly in comment) and I found you have already add configuration such as
split_policy and flush_policy in admin.create() method. I think maybe we should
add the same logic in admin.alter() method or I missed the code . Hope to hear
from you.Thanks.
> SPLIT_POLICY and FLUSH_POLICY cann't be set directly by hbase shell
> -------------------------------------------------------------------
>
> Key: HBASE-19340
> URL: https://issues.apache.org/jira/browse/HBASE-19340
> Project: HBase
> Issue Type: Bug
> Affects Versions: 1.2.6
> Reporter: zhaoyuan
> Assignee: zhaoyuan
> Fix For: 1.2.8
>
> Attachments: HBASE-19340-branch-1.2.batch
>
>
> Recently I wanna try to alter the split policy for a table on my cluster
> which version is 1.2.6 and as far as I know The SPLIT_POLICY is an attribute
> of the HTable so I run the command in hbase shell console below.
> alter 'tablex',SPLIT_POLICY =>
> 'org.apache.hadoop.hbase.regionserver.DisabledRegionSplitPolicy'
> However, It gave the information like this and I confused
> Unknown argument ignored: SPLIT_POLICY
> Updating all regions with the new schema...
> So I check the source code That admin.rb might miss the setting for this
> argument .
> htd.setMaxFileSize(JLong.valueOf(arg.delete(MAX_FILESIZE))) if
> arg[MAX_FILESIZE]
> htd.setReadOnly(JBoolean.valueOf(arg.delete(READONLY))) if arg[READONLY]
> ...
> So I think it may be a bug ,is it?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
