See https://builds.apache.org/job/Hadoop-Common-trunk/1094/changes
Changes:
[kasha] YARN-1784. TestContainerAllocation assumes CapacityScheduler. (Robert
Kanter via kasha)
[jing9] HADOOP-10475. ConcurrentModificationException in
AbstractDelegationTokenSelector.selectToken(). Contributed by
A Java 8 runtime would also offer transparent performance improvements like
a reimplementation of ConcurrentSkipListMap, C2 support for AES cipher
acceleration with native CPU instructions, perf improvements for going from
String to byte[] or vice versa, and IIRC after 8u20 monitor lock elision
I think this thread isn't so much about whether java7, 8 etc features
are valuable, they are useful of course, and we'll want to adopt them,
it's a question of how we adopt them and in which releases.
For the sake of this discussion we should separate the runtime from
the programming APIs. Users
Haohui Mai created HADOOP-10487:
---
Summary: Racy code in UserGroupInformation#ensureInitialized()
Key: HADOOP-10487
URL: https://issues.apache.org/jira/browse/HADOOP-10487
Project: Hadoop Common
+1 for keeping jdk 6 suppprt in branch-2 and start using jdk 7 in trunk.
I agree that this approach makes patch generation difficult for branch-2
and trunk.
Also the actual benefit and real issues after start using jdk7 will be
known only if atleast one of the release is out in trunk version.
Alejandro Abdelnur created HADOOP-10488:
---
Summary: TestKeyProviderFactory fails randomly
Key: HADOOP-10488
URL: https://issues.apache.org/jira/browse/HADOOP-10488
Project: Hadoop Common
