Apache Hadoop qbt Report: branch2+JDK7 on Linux/x86

2019-09-22 Thread Apache Jenkins Server
For more details, see https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/453/ No changes -1 overall The following subsystems voted -1: compile findbugs hadolint mvninstall mvnsite pathlen unit xml The following subsystems voted -1 but were configured to be

Re: [NOTICE] Building trunk needs protoc 3.7.1

2019-09-22 Thread Vinayakumar B
Thanks Steve. Idea is not to shade all artifacts. Instead maintain one artifact ( hadoop-thirdparty) which have all such dependencies ( com.google.* may be), add this artifact as dependency in hadoop modules. Use shaded classes directly in the code of hadoop modules instead of shading at package

[jira] [Resolved] (HADOOP-16592) Build fails as can't retrieve websocket-server-impl

2019-09-22 Thread Steve Loughran (Jira)
[ https://issues.apache.org/jira/browse/HADOOP-16592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Loughran resolved HADOOP-16592. - Resolution: Works for Me > Build fails as can't retrieve websocket-server-impl >

Re: [NOTICE] Building trunk needs protoc 3.7.1

2019-09-22 Thread Steve Loughran
On Sun, Sep 22, 2019 at 3:22 PM Vinayakumar B wrote: >Protobuf provides Wire compatibility between releases.. but not > guarantees the source compatibility in generated sources. There will be a > problem in compatibility if anyone uses generated protobuf message outside > of Hadoop modules.

Re: [NOTICE] Building trunk needs protoc 3.7.1

2019-09-22 Thread Vinayakumar B
Protobuf provides Wire compatibility between releases.. but not guarantees the source compatibility in generated sources. There will be a problem in compatibility if anyone uses generated protobuf message outside of Hadoop modules. Which ideally shouldn't be as generated sources are not public

Re: [NOTICE] Building trunk needs protoc 3.7.1

2019-09-22 Thread Vinod Kumar Vavilapalli
Quick question, being lazy here, lots of JIRA updates on HADOOP-13363 over the years not helping either. Does anyone know what this upgrade will mean w.r.t compatibility for the Hadoop releases themselves? Remember that trunk is still 3.x. Thanks +Vinod > On Sep 21, 2019, at 9:55 AM,

Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk source tree

2019-09-22 Thread Vinod Kumar Vavilapalli
Looks to me that the advantages of this additional step are only incremental given that you've already decoupled releases and dependencies. Do you see a Submarine like split-also-into-a-TLP for Ozone? If not now, sometime further down the line? If so, why not do both at the same time? I felt

Re: [VOTE] Release Apache Hadoop 3.2.1 - RC0

2019-09-22 Thread Rohith Sharma K S
Inline comments On Thu, 19 Sep 2019 at 11:51, Rohith Sharma K S wrote: > Thanks Brahma for voting and bringing this to my attention! > > On Thu, 19 Sep 2019 at 11:28, Brahma Reddy Battula > wrote: > >> RohithThanks for driving the release >> >> +1 (Binding). >> >> --Built from the source >>

Re: [VOTE] Release Apache Hadoop 3.2.1 - RC0

2019-09-22 Thread Rohith Sharma K S
Thanks all who helped to verify and vote 3.2.1 release! I am concluding the vote for 3.2.1 RC0. Summary of votes for hadoop-3.2.1-RC0: 7 binding +1s, from: -- Sunil Govindan, Brahma Reddy Battula, Steve Loughran, Elek, Marton, Weiwei Yang, Naganarasimha Garla, Rohith