[jira] [Commented] (HBASE-7272) HFileOutputFormat.configureIncrementalLoad should honor table Max File Size and Columns BlockSize

["Anoop Sam John (JIRA)" <ji...@apache.org>]

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

Anoop Sam John commented on HBASE-7272:
---------------------------------------

Checked the 92 code base.

final long maxsize = conf.getLong("hbase.hregion.max.filesize",
        HConstants.DEFAULT_MAX_FILE_SIZE);
    final int blocksize = conf.getInt("hbase.mapreduce.hfileoutputformat.blocksize",
        HFile.DEFAULT_BLOCKSIZE);

Here by we set max file size and block size. For this we need to specify the values as config values. Table descriptor wont be available at the incremental load time. So wont be able to take the values from HTD as such.

I think there is no issue.. Pls correct me if I am missing some thing..


                
> HFileOutputFormat.configureIncrementalLoad should honor table Max File Size and Columns BlockSize
> -------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-7272
>                 URL: https://issues.apache.org/jira/browse/HBASE-7272
>             Project: HBase
>          Issue Type: Improvement
>          Components: HFile
>    Affects Versions: 0.92.1
>            Reporter: Randy Fox
>            Priority: Minor
>
> HFileOutputFormat.configureIncrementalLoad is used to generate HFiles matching region assignments.  The problem is that is it does not using file and block size settings.  This can create a lot of files of wrong block size, which may take a long time to compact.  I think it should honor these settings and expedite its use.

--
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