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 EE85E10A6B for ; Fri, 19 Jul 2013 09:44:51 +0000 (UTC) Received: (qmail 53914 invoked by uid 500); 19 Jul 2013 09:44:51 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 53790 invoked by uid 500); 19 Jul 2013 09:44:50 -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 53765 invoked by uid 99); 19 Jul 2013 09:44:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jul 2013 09:44:50 +0000 Date: Fri, 19 Jul 2013 09:44:50 +0000 (UTC) From: "Anoop Sam John (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (HBASE-8949) hbase.mapreduce.hfileoutputformat.blocksize should configure with blocksize of a table 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-8949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713495#comment-13713495 ] Anoop Sam John edited comment on HBASE-8949 at 7/19/13 9:43 AM: ---------------------------------------------------------------- The change looks reasonable to me. Only one concern is before this patch , for all the data import, block size being used was value of "hbase.mapreduce.hfileoutputformat.blocksize". If some one changed this conf value in xml for changing the block size during bulk load, from now on that wont get applied right? was (Author: anoop.hbase): The change looks reasonable to me. Only one concern is before this patch , for all the data import block size being used was value of "hbase.mapreduce.hfileoutputformat.blocksize". If some one changes this conf value in xml for changing the block size during bulk load, from now on that wont get applied right? > hbase.mapreduce.hfileoutputformat.blocksize should configure with blocksize of a table > -------------------------------------------------------------------------------------- > > Key: HBASE-8949 > URL: https://issues.apache.org/jira/browse/HBASE-8949 > Project: HBase > Issue Type: Bug > Components: mapreduce > Reporter: rajeshbabu > Assignee: rajeshbabu > Fix For: 0.98.0, 0.95.2, 0.94.11 > > Attachments: HBASE-8949_94.patch, HBASE-8949_trunk.patch > > > While initializing mapreduce job we are not configuring hbase.mapreduce.hfileoutputformat.blocksize, so hfiles are always creating with 64kb (default)block size even though tables has different block size. > We need to configure it with block size from table descriptor. -- 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