Re: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

> On Jul 22, 2016, at 5:47 PM, Zheng, Kai wrote: > > For the leveldb thing, wouldn't we have an alternative option in Java for the > platforms where leveldb isn't supported yet due to whatever reasons. IMO, > native library would be best to be used for optimization and

Re: Setting JIRA fix versions for 3.0.0 releases

> On Jul 22, 2016, at 7:16 PM, Andrew Wang wrote: > > Does this mean you find our current system of listing a JIRA as being fixed > in both a 2.6.x and 2.7.x to be confusing? Nope. I'm only confused when there isn't a .0 release in the fix line. When I see

Re: Setting JIRA fix versions for 3.0.0 releases

Thanks for the input Allen, good perspective as always, inline: > From the perspective of an end user who is reading multiple > versions' listings at once, listing the same JIRA being fixed in multiple > releases is totally confusing, especially now that release notes are > actually

RE: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

For the leveldb thing, wouldn't we have an alternative option in Java for the platforms where leveldb isn't supported yet due to whatever reasons. IMO, native library would be best to be used for optimization and production for performance. For development and pure Java platform, by default

Re: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

But if I don't use ApplicationClassLoader, my java app is basically screwed then, right? Also: right now, the non-Linux and/or non-x86 platforms have to supply their own leveldbjni jar (or at least the C level library?) in order to make YARN even functional. How is that going to work with

Re: Setting JIRA fix versions for 3.0.0 releases

I’ve been using jdiff simply because of a lack of alternative. If you’ve had experience with tool [1], if you think it serves our purpose, and if you can spare some time, that’ll be greatly appreciated. I can also pitch in with whatever help is needed. I think we should pick one of 2.6.3 or

Re: Setting JIRA fix versions for 3.0.0 releases

From the perspective of an end user who is reading multiple versions' listings at once, listing the same JIRA being fixed in multiple releases is totally confusing, especially now that release notes are actually readable. "So which version was it ACTUALLY fixed in?" is going to be the

Re: Setting JIRA fix versions for 3.0.0 releases

> > >> I am also not quite sure I understand the rationale of what's in the > HowToCommit wiki. Assuming the semantic versioning (http://semver.org) as > our baseline thinking, having concurrent release streams alone breaks the > principle. And that is *regardless of* how we line up individual

Re: Setting JIRA fix versions for 3.0.0 releases

On Thu, Jul 21, 2016 at 3:58 PM, Andrew Wang wrote: > Thanks for the input Vinod, inline: > > > > Similarly the list of features we are enabling in this alpha would be > good > > - may be update the Roadmap wiki. Things like classpath-isolation which > > were part of

Re: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

The work on HADOOP-13070 and the ApplicationClassLoader are generic and go beyond YARN. It can be used in any JVM that uses hadoop. The current use cases are MR containers, hadoop's RunJar (as in "hadoop jar"), and the YARN node manager auxiliary services. I'm not sure if that's what you were

[jira] [Created] (MAPREDUCE-6744) Increase timeout on TestDFSIO tests

Eric Badger created MAPREDUCE-6744: -- Summary: Increase timeout on TestDFSIO tests Key: MAPREDUCE-6744 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6744 Project: Hadoop Map/Reduce

Re: [DISCUSS] The order of classpath isolation work and updating/shading dependencies on trunk

Does any of this work actually help processes that sit outside of YARN? > On Jul 21, 2016, at 12:29 PM, Sean Busbey wrote: > > thanks for bringing this up! big +1 on upgrading dependencies for 3.0. > > I have an updated patch for HADOOP-11804 ready to post this week. I've

[jira] [Created] (MAPREDUCE-6743) nativetask unit tests need to provide usable output

Allen Wittenauer created MAPREDUCE-6743: --- Summary: nativetask unit tests need to provide usable output Key: MAPREDUCE-6743 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6743 Project:

[jira] [Resolved] (MAPREDUCE-6742) Test

[ https://issues.apache.org/jira/browse/MAPREDUCE-6742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Wittenauer resolved MAPREDUCE-6742. - Resolution: Not A Problem > Test > > > Key:

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/110/ [Jul 21, 2016 11:41:02 PM] (xiao) HDFS-10225. DataNode hot swap drives should disallow storage type [Jul 22, 2016 6:21:47 AM] (cdouglas) HADOOP-13393. Omit unsupported fs.defaultFS setting in ADLS -1

[jira] [Created] (MAPREDUCE-6742) Test

Prashanth G B created MAPREDUCE-6742: Summary: Test Key: MAPREDUCE-6742 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6742 Project: Hadoop Map/Reduce Issue Type: Bug

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

For more details, see https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/109/ No changes -1 overall The following subsystems voted -1: asflicense unit The following subsystems voted -1 but were configured to be filtered/ignored: cc checkstyle javac javadoc pylint