For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1283/
[Oct 7, 2019 4:04:36 AM] (shashikant) HDDS-2169. Avoid buffer copies while
submitting client requests in
[Oct 7, 2019 7:38:08 AM] (aajisaka) HADOOP-16512. [hadoop-tools] Fix order of
actual and expected
Steve Loughran created HADOOP-16644:
---
Summary: Intermittent failure of ITestS3ATerasortOnS3A: timestamp
differences
Key: HADOOP-16644
URL: https://issues.apache.org/jira/browse/HADOOP-16644
Wei-Chiu Chuang created HADOOP-16643:
Summary: Upate netty4 to the latest 4.1.42
Key: HADOOP-16643
URL: https://issues.apache.org/jira/browse/HADOOP-16643
Project: Hadoop Common
Issue
Steve Loughran created HADOOP-16642:
---
Summary: ITestDynamoDBMetadataStoreScale failing as the error text
does not match expectations
Key: HADOOP-16642
URL: https://issues.apache.org/jira/browse/HADOOP-16642
I spent the whole last week cherry picking commits from trunk/branch-3.2 to
branch-3.1 (should've done this prior to 3.1.4 code freeze). There were
about 50-60 of them, many of them are conflict-free, and several of them
are critical bug fixes.
If your commit stays in trunk, it'll be useless for
To be honest, I have no idea. I don't know about the historical meaning.
But as there is no other feedback, here are my guesses based on pure logic:
* current -> should point to the release with the highest number (3.2.1)
* stable -> to the stable 3.x release with the highest number (3.2.1
