[
https://issues.apache.org/jira/browse/HBASE-28447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828954#comment-17828954
]
Wellington Chevreuil commented on HBASE-28447:
----------------------------------------------
[~bbeaudreault] , I think [~gourab.taparia] means a global config property that
would go on hbase-site.xml. IIRC, currently we just make it configurable at
table or CF level, meaning if you want to change it for all your schema, you
need to update that individually for all tables/CFs. Is that right,
[~gourab.taparia] ?
> New configuration to override the hfile specific blocksize
> ----------------------------------------------------------
>
> Key: HBASE-28447
> URL: https://issues.apache.org/jira/browse/HBASE-28447
> Project: HBase
> Issue Type: Improvement
> Reporter: Gourab Taparia
> Assignee: Gourab Taparia
> Priority: Minor
>
> Right now there is no config attached to the HFile block size by which we can
> override the default. The default is set to 64 KB in
> HConstants.DEFAULT_BLOCKSIZE . We need a new config which can control this
> value.
> Since the BLOCKSIZE is tracked at the column family level - we will need to
> respect the CFD value first. Also, configuration settings are also something
> that can be set in schema, at the column or table level, and will override
> the relevant values from the site file. Below is the precedence order we can
> use to get the final blocksize value :
> {code:java}
> ColumnFamilyDescriptor.BLOCKSIZE > schema level site configuration overrides
> > site configuration > HConstants.DEFAULT_BLOCKSIZE{code}
> PS: There is one related config “hbase.mapreduce.hfileoutputformat.blocksize”
> however that is specific to map-reduce jobs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
