Unfortunately, it turns out to be a regression in addition to a breaking change.
In short, HADOOP-19098 (or more) makes Hadoop 3.4.1 fails even when users give
disjoint ranges.
I filed a Hadoop JIRA issue and a PR. Please take a look at that.
- HADOOP-19291. `CombinedFileRange.merge` should not
Dongjoon Hyun created HADOOP-19291:
--
Summary: `CombinedFileRange.merge` should not convert disjoint
ranges into overlapped ones
Key: HADOOP-19291
URL: https://issues.apache.org/jira/browse/HADOOP-19291
Thank you for 3.4.1 RC2.
HADOOP-19098 (Vector IO: consistent specified rejection of overlapping ranges)
seems to be a hard breaking change at 3.4.1.
Do you think we can have an option to handle the overlapping ranges in Hadoop
layer instead of introducing a breaking change to the users at the m
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-trunk-java8-linux-x86_64/1714/
[Sep 27, 2024, 4:46:28 AM] (github) HADOOP-19284: [ABFS] Allow
"fs.azure.account.hns.enabled" to be set as Account Specific Config (#7062)
[Sep 27, 2024, 8:56:09 AM] (github) HDFS-17624. Fix
DFSNetw
[
https://issues.apache.org/jira/browse/HADOOP-19290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ayush Saxena resolved HADOOP-19290.
---
Fix Version/s: 3.5.0
Hadoop Flags: Reviewed
Resolution: Fixed
> Operating on /
For more details, see
https://ci-hadoop.apache.org/job/hadoop-qbt-branch-2.10-java7-linux-x86_64/1529/
No changes
-1 overall
The following subsystems voted -1:
asflicense hadolint mvnsite pathlen unit
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc
