Duo Zhang created HADOOP-16598:
--
Summary: Backport "HADOOP-16558 [COMMON+HDFS] use
protobuf-maven-plugin to generate protobuf classes" to all active branches
Key: HADOOP-16598
URL:
Hi,
Thank you all who spent time to verify and vote 3.1.3 release!
I‘m pleased to announce that the vote for 3.1.3 RC0 passed! I'll push the
release bits and send out an announcement for 3.1.3 soon.
Summary of votes for Hadoop-3.1.3-RC0:
4 binding +1s, from Rohith Sharma K S, Sunil Govindan,
Duo Zhang created HADOOP-16597:
--
Summary: Backport the protobuf maven plugin change to all active
branches
Key: HADOOP-16597
URL: https://issues.apache.org/jira/browse/HADOOP-16597
Project: Hadoop
Siddharth Seth created HADOOP-16599:
---
Summary: Allow a SignerInitializer to be specified along with a
Custom Signer
Key: HADOOP-16599
URL: https://issues.apache.org/jira/browse/HADOOP-16599
[
https://issues.apache.org/jira/browse/HADOOP-16600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lisheng Sun resolved HADOOP-16600.
--
Resolution: Duplicate
> StagingTestBase uses methods not available in Mockito 1.8.5 in
Lisheng Sun created HADOOP-16600:
Summary: StagingTestBase uses methods not available in Mockito
1.8.5 in branch-3.1
Key: HADOOP-16600
URL: https://issues.apache.org/jira/browse/HADOOP-16600
Project:
[
https://issues.apache.org/jira/browse/HADOOP-16600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lisheng Sun reopened HADOOP-16600:
--
> StagingTestBase uses methods not available in Mockito 1.8.5 in branch-3.1
>
MacChen01 created HADOOP-16601:
--
Summary: Add support for hardware crc32 of nativetask checksums on
aarch64 arch
Key: HADOOP-16601
URL: https://issues.apache.org/jira/browse/HADOOP-16601
Project: Hadoop
Hi devs and users,
Tomorrow (sorry for the short notice) we will do a presentation at Strata
Data Conf @ NY for a Community update of Hadoop 3.x. I'm thinking to create
a slide about existing production deployment on Hadoop 3.x. Basically, I
want to put a logo wall with a list of big names so we
We (Verizon Media) are currently moving towards upgrading our clusters from
our internal fork of branch-2.8 to an internal fork of branch-2. During
this process, we have found multiple incompatible changes in protobufs
between branch-2.8 and branch-2. These incompatibilities were all
introduced
Hi Eric, thanks for the investigation.
- For YARN-6616, for branch-2.8 and below, it was only committed to
2.7.8/2.8.6 which have not been released (as I understand). Perhaps we can
revert YARN-6616 from branch-2.7 and branch-2.8.
- For YARN-6050, there's a bit here:
[
https://issues.apache.org/jira/browse/HADOOP-16560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinayakumar B resolved HADOOP-16560.
Fix Version/s: 3.3.0
Hadoop Flags: Reviewed
Resolution: Fixed
Merged already
[
https://issues.apache.org/jira/browse/HADOOP-16561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinayakumar B resolved HADOOP-16561.
Fix Version/s: 3.3.0
Hadoop Flags: Reviewed
Resolution: Fixed
Merged to
Vinayakumar B created HADOOP-16595:
--
Summary: [pb-upgrade] Create hadoop-thirdparty artifact to have
shaded protobuf
Key: HADOOP-16595
URL: https://issues.apache.org/jira/browse/HADOOP-16595
Vinayakumar B created HADOOP-16596:
--
Summary: [pb-upgrade] Use shaded protobuf classes from
hadoop-thirdparty dependency
Key: HADOOP-16596
URL: https://issues.apache.org/jira/browse/HADOOP-16596
* For YARN-6616, for branch-2.8 and below, it was only committed to
2.7.8/2.8.6 which have not been released (as I understand). Perhaps we can
revert YARN-6616 from branch-2.7 and branch-2.8.
- This seems reasonable. Since we haven't released anything, it should be
no issue to change the
Sorry, let me edit my first point. We can just create addendums for YARN-6616
in branch-2.7 and branch-2.8 to edit the submitTime field to the correct id 28.
We don’t need to revert YARN-6616 from these branches completely.
Jonathan
From: Jonathan Hung
Sent:
- I've created YARN-9855 and uploaded patches to fix YARN-6616 in
branch-2.8 and branch-2.7.
- For YARN-6050, not sure either. Robert/Wangda, can you comment on
YARN-6050 compatibility?
- For YARN-7813, not sure why moving from 2.8.4/5 -> 2.8.6 would be
incompatible with this strategy? It should
18 matches
Mail list logo