[
https://issues.apache.org/jira/browse/HBASE-25431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282169#comment-17282169
]
Hudson commented on HBASE-25431:
--------------------------------
Results for branch branch-2.4
[build #48 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/48/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.4/48/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.4/48/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.4/48/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.4/48/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}
> MAX_FILESIZE and MEMSTORE_FLUSHSIZE should not be set negative number
> ---------------------------------------------------------------------
>
> Key: HBASE-25431
> URL: https://issues.apache.org/jira/browse/HBASE-25431
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 3.0.0-alpha-1, 2.4.0
> Reporter: Baiqiang Zhao
> Assignee: Baiqiang Zhao
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.5.0
>
> Attachments: image-2020-12-22-11-46-38-967.png
>
>
> Before create or alter table, we will do sanityCheck in
> TableDescriptorChecker. If MAX_FILESIZE or MEMSTORE_FLUSHSIZE < 0, use
> maxFileSizeLowerLimit or flushSizeLowerLimit instead to pass check. But the
> real value in TableDescriptor is still < 0, and we can see negative values
> on the UI.
> However in flush and split logic, MAX_FILESIZE and MEMSTORE_FLUSHSIZE will
> judge whether it's value <= 0 , if true, change to default value. This does
> not affect flush and split.
> !image-2020-12-22-11-46-38-967.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
