[VOTE] Merge yarn-native-services branch into trunk

Hi All, I would like to call a vote for merging yarn-native-services to trunk. The vote will run for 7 days as usual. At a high level, the following are the key feautres implemented. - YARN-5079[1]. A native YARN framework (ApplicationMaster) to migrate and orchestrate existing services to

Re: native folder not found in hadoop-common build on Ubuntu

Thanks Allen for the information. No wonder I got it on Windows automatically. By the way, with John and Ravi's help, I was able to have it work now by installing CMake as well as Zlib (I already had Protobuf installed before). Thanks everyone!! Ping On Thu, Aug 31, 2017 at 7:03 PM, Allen

[jira] [Resolved] (HADOOP-14817) shelldocs fails mvn site

[ https://issues.apache.org/jira/browse/HADOOP-14817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved HADOOP-14817. --- Resolution: Fixed > shelldocs fails mvn site > > >

Re: native folder not found in hadoop-common build on Ubuntu

Just to close the loop on this a bit ... Windows always triggers the 'native-win' profile because winutils is currently required to actually use Apache Hadoop on that platform. On other platforms, the 'native' profile is optional since their is enough support in the JDK to at least

[jira] [Created] (HADOOP-14824) Update azure datalake connector to use current version of the datalake SDK

Atul Sikaria created HADOOP-14824: - Summary: Update azure datalake connector to use current version of the datalake SDK Key: HADOOP-14824 URL: https://issues.apache.org/jira/browse/HADOOP-14824

Re: native folder not found in hadoop-common build on Ubuntu

Hi Ravi, John, Thanks! Yeah, it's the first profile. Now as I tried the build with -Pnative, I saw the build failure. It complains for cmake. It's also a requirement specified in BUILDING.txt that John pointed out. Thanks!! Ping On Thu, Aug 31, 2017 at 4:03 PM, Ravi Prakash

[jira] [Reopened] (HADOOP-14674) Correct javadoc for getRandomizedTempPath

[ https://issues.apache.org/jira/browse/HADOOP-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang reopened HADOOP-14674: -- I don't see this showing up in trunk, did it actually get committed? > Correct javadoc for

Re: native folder not found in hadoop-common build on Ubuntu

Please use -Pnative profile On Thu, Aug 31, 2017 at 3:53 PM, Ping Liu wrote: > Hi John, > > Thank you for your quick response. > > I used > > mvn clean install -DskipTests > > I just did a comparison with my Windows build result. winutils is missing > too. > > So both

Re: native folder not found in hadoop-common build on Ubuntu

Hi John, Thank you for your quick response. I used mvn clean install -DskipTests I just did a comparison with my Windows build result. winutils is missing too. So both "native" and "winutils" folders are not generated in target folder, although it shows BUILD SUCCESS. Thanks. Ping On

Re: native folder not found in hadoop-common build on Ubuntu

Hi Ping, Thanks for using Hadoop. Linux is Unix-like. Hadoop supports native code on Linux. Please read BUILDING.txt in the root of the Hadoop source tree. Could you provide the entire Maven command line when you built Hadoop? On Thu, Aug 31, 2017 at 3:06 PM, Ping Liu

native folder not found in hadoop-common build on Ubuntu

I built hadoop-common on Ubuntu in my VirtualBox. But in target folder, I didn't find "native" folder that is supposed to contain the generated JNI header files for C. On my Windows, native folder is found in target. As I check the POM file, I found "native build only supported on Mac or Unix".

Re: [VOTE] Merge feature branch YARN-5355 (Timeline Service v2) to trunk

Good to see this merged. I have initiated a separate thread with a smaller set of stakeholders to discuss inclusion in 2.9. We'll report back to the 2.9 release thread as soon as we reach consensus. On Thu, Aug 31, 2017 at 10:39 AM, Ravi Prakash wrote: > +1 to maintaining

Re: [VOTE] Merge feature branch YARN-5355 (Timeline Service v2) to trunk

+1 to maintaining history. On Wed, Aug 30, 2017 at 11:38 PM, varunsax...@apache.org < varun.saxena.apa...@gmail.com> wrote: > Yes, I had used "git merge --no-ff" while merging ATSv2 to trunk. > Maintaining history I believe can be useful as it can make reverts > easier if at all required. > And

Apache Hadoop qbt Report: trunk+JDK8 on Linux/x86

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/509/ [Aug 30, 2017 7:28:56 AM] (rakeshr) HDFS-12258. ec -listPolicies should list all policies in system, no [Aug 30, 2017 2:54:30 PM] (aajisaka) Revert "HADOOP-14671. Upgrade to Apache Yetus 0.5.0." [Aug 30,

[jira] [Resolved] (HADOOP-14772) Audit-log delegation token related operations to the KMS

[ https://issues.apache.org/jira/browse/HADOOP-14772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Chen resolved HADOOP-14772. Resolution: Won't Fix Closing as won't fix for now, due to above comment. > Audit-log delegation

[jira] [Created] (HADOOP-14823) hadoop-dist build to verify that shell profiles are created

Steve Loughran created HADOOP-14823: --- Summary: hadoop-dist build to verify that shell profiles are created Key: HADOOP-14823 URL: https://issues.apache.org/jira/browse/HADOOP-14823 Project: Hadoop

[jira] [Created] (HADOOP-14822) hadoop-project/pom.xml is exectable

Akira Ajisaka created HADOOP-14822: -- Summary: hadoop-project/pom.xml is exectable Key: HADOOP-14822 URL: https://issues.apache.org/jira/browse/HADOOP-14822 Project: Hadoop Common Issue

Re: [DISCUSS] Merge yarn-native-services branch into trunk

Update: I’ve chatted with Andrew offline, we’ll proceed with merging yarn-native-services into trunk for beta. We’ll advertise this feature as “alpha" Currently, we have completed all the jiras for this merge - I’ve also moved out the subtasks that are not blocking this merge. I’ve created

Re: [VOTE] Merge feature branch YARN-5355 (Timeline Service v2) to trunk

Yes, I had used "git merge --no-ff" while merging ATSv2 to trunk. Maintaining history I believe can be useful as it can make reverts easier if at all required. And can be an easy reference point to look at who had contributed what without having to go back to the branch. Regards, Varun Saxena.