Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CFDC911CA1 for ; Wed, 9 Apr 2014 20:30:24 +0000 (UTC) Received: (qmail 11735 invoked by uid 500); 9 Apr 2014 20:30:17 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 11683 invoked by uid 500); 9 Apr 2014 20:30:16 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 11673 invoked by uid 99); 9 Apr 2014 20:30:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Apr 2014 20:30:16 +0000 Date: Wed, 9 Apr 2014 20:30:16 +0000 (UTC) From: "Jeremy Carroll (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-10603) Deprecate RegionSplitter CLI tool MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-10603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964631#comment-13964631 ] Jeremy Carroll commented on HBASE-10603: ---------------------------------------- FWIW we currently use the org.apache.hadoop.hbase.util.RegionSplitter with online rolling splits to perform capacity planning on live clusters. The HBase shell only allows for Splits for newly created tables I believe. > Deprecate RegionSplitter CLI tool > --------------------------------- > > Key: HBASE-10603 > URL: https://issues.apache.org/jira/browse/HBASE-10603 > Project: HBase > Issue Type: Improvement > Components: util > Reporter: Nick Dimiduk > Priority: Minor > Labels: noob > Fix For: 0.99.0 > > > RegionSplitter is a utility for partitioning a table based on some split algorithm. Those same algorithms are exposed via the shell create command. There's no value in having two ways to access the same functionality. Ensure the main method doesn't provide any functionality absent from the shell and remove it. -- This message was sent by Atlassian JIRA (v6.2#6252)