Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 22 Feb 2013 23:06:13 +0000 (UTC)
From: "Nick Dimiduk (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12632488.1360881622982.326153.1361574373635@arcas>
In-Reply-To: <JIRA.12632488.1360881622982@arcas>
References: <JIRA.12632488.1360881622982@arcas>
Subject: [jira] [Commented] (HBASE-7850) Bulkload final step can detect and
 pre-split tables
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Nick Dimiduk commented on HBASE-7850:
-------------------------------------

When you say "final step of bulkload", are you speaking of the CompleteBulkLoad application, or a MR job ending in HFileOutputFormat?
                
> Bulkload final step can detect and pre-split tables
> ---------------------------------------------------
>
>                 Key: HBASE-7850
>                 URL: https://issues.apache.org/jira/browse/HBASE-7850
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>            Reporter: Harsh J
>            Priority: Minor
>
> Many new devs (read: POC folks?) aren't aware of the pre-split feature of table creation, given that its mostly manual. This leads to situations where a huge amount of data gets loaded into a single or a small set of regions, causing further issues such as non-assignment or lack of performance.
> Given that the final step of bulkload has a good picture of what they keys may look like, it could split the table first if it detects certain conditions (we can go over this in comments) and then perform the bulkload.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira