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

Hudson commented on HBASE-26316:
--------------------------------

Results for branch branch-2
        [build #370 on 
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/370/]:
 (x) *{color:red}-1 overall{color}*
----
details (if available):

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/370/General_20Nightly_20Build_20Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/370/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/370/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/370/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Per-table or per-CF compression codec setting overrides
> -------------------------------------------------------
>
>                 Key: HBASE-26316
>                 URL: https://issues.apache.org/jira/browse/HBASE-26316
>             Project: HBase
>          Issue Type: Sub-task
>          Components: HFile, Operability
>    Affects Versions: 2.5.0, 3.0.0-alpha-2
>            Reporter: Andrew Kyle Purtell
>            Assignee: Andrew Kyle Purtell
>            Priority: Minor
>             Fix For: 2.5.0, 3.0.0-alpha-2
>
>
> This won't work as expected today...
> {noformat}
> hbase> create 'sometable', \
>   { NAME => 'somefamily', VERSIONS => 1000, COMPRESSION => 'ZSTD' }, \
>   CONFIGURATION => { 'hbase.io.compress.zstd.level' => '9' }
> {noformat}
> ... but it should. We get and retain Compressor instances in 
> HFileBlockDefaultEncodingContext, and could in theory call Compressor#reinit 
> when setting up the context, to update compression parameters like 
> compression level and buffer size per the ambient configuration, but we do 
> not plumb through the CompoundConfiguration from the Store into 
> HFileBlockDefaultEncodingContext. Instead can only update codec parameters 
> globally in system site conf files.
> This is actually pretty important for algorithms like ZSTD, which offers more 
> than 20 different compression levels, where at level 1 it is almost as fast 
> at compression as LZ4, and where at levels > 19 it utilizes computationally 
> expensive techniques to rival LZMA at compression ratio (and poor compression 
> speed). It is very likely that the ZSTD level you'd want to employ for a 
> given table's data will vary by use case.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to