[
https://issues.apache.org/jira/browse/HBASE-6182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466098#comment-13466098
]
Andrew Purtell commented on HBASE-6182:
---------------------------------------
bq. I'm wondering if we shouldn't make this a blocker and convert the 0.96
jenkins build to be on jdk7. I say this because talking to Nicolas today, there
are perf wins running on jdk7 (though compare was to jdk6u14 which is kinda
old)... I can try measuring myself to see if a diff between u31 say.
+1
There are other reasons to do this too. Java 6 is to be EOLed this November
IIRC. Our prod is going to want to move to JRE 7 some time next year, it's not
acceptable to have a dependency on something EOLed.
Right now there are a lot of unit tests for various components that fail if
built and run on JDK 7 (ZooKeeper, Hadoop core, HDFS, HBase, Pig, ...). If you
look over the commit streams for these projects, many of the unit test failures
are issues with the unit tests themselves. We're requiring JDK 6 for build but
requiring cluster tests with JRE 7 to pass.
> Make HBase works with jdk1.7
> ----------------------------
>
> Key: HBASE-6182
> URL: https://issues.apache.org/jira/browse/HBASE-6182
> Project: HBase
> Issue Type: Task
> Reporter: Jimmy Xiang
> Priority: Critical
> Fix For: 0.96.0
>
> Attachments: large-tests.log, medium-tests.log
>
>
> jdk1.7 is out for a while. HBase should support it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
