[
https://issues.apache.org/jira/browse/HBASE-30403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18117920#comment-18117920
]
Hudson commented on HBASE-30403:
--------------------------------
Results for branch branch-2
[build #156 on
builds.a.o|https://ci-hbase.apache.org/job/HBase-Integration-Test/job/branch-2/156/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 client integration test for 2.10.2 {color}
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.5 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.3.6 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.0 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.1 {color}
(/) {color:green}+1 client integration test for 3.4.1 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.2 {color}
(/) {color:green}+1 client integration test for 3.4.2 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.3 {color}
(/) {color:green}+1 client integration test for 3.4.3 with shaded hadoop
client{color}
> CustomDateTieredCompactionPolicy#getCompactBoundariesForMajor drops the
> cutOffTimestamp boundary when files lack CUSTOM_TIERING_TIME_RANGE
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-30403
> URL: https://issues.apache.org/jira/browse/HBASE-30403
> Project: HBase
> Issue Type: Bug
> Components: Compaction
> Affects Versions: 3.0.0, 2.6.7
> Reporter: Jeremy Schoemaker
> Assignee: Jeremy Schoemaker
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.1, 2.6.8
>
>
> getCompactBoundariesForMajor derives the major-compaction boundaries from the
> CUSTOM_TIERING_TIME_RANGE file-info tag of every file in filesToCompact.
> Files written before custom tiering was enabled (or by any writer that does
> not set the tag) contribute nothing, so with a mixed or untagged set the
> min/max traversal produces a boundary list that never contains the
> cutOffTimestamp split. The major compaction then writes a single tier instead
> of separating hot and cold cells.
> Fix (PR https://github.com/apache/hbase/pull/8573): always return
> [Long.MIN_VALUE, cutOffTimestamp] without traversing filesToCompact. This is
> safe because CustomTieringMultiFileWriter#append already buckets each cell by
> these boundaries and only commits a file for a tier that actually received
> data, so an empty tier never produces an empty HFile. The five tests in
> TestCustomCellTieredCompactionPolicy and TestCustomCellTieredCompactor that
> asserted boundary counts derived from the old tag traversal are updated to
> the new intended behavior in the same PR.
> Review thread with wchevreuil on the PR agreed the simplified approach on
> 2026-08-26; this ticket is filed at his request so the change can be merged.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
