[
https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498101#comment-13498101
]
Andy Jefferson commented on HIVE-3632:
--------------------------------------
You refer to a DataNucleus JIRA issue that was marked fixed in June 2012. How
does that imply that "they don't plan to actively support JDK7+ bytecode any
time soon" ? DataNucleus 3.1.x supports JDK1.7+ and has for some time. There
are 0 reported problems using DataNucleus v3.1 with JDK1.7. You don't define
"not successful"
> datanucleus breaks when using JDK7
> ----------------------------------
>
> Key: HIVE-3632
> URL: https://issues.apache.org/jira/browse/HIVE-3632
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.10.0, 0.9.1
> Reporter: Chris Drome
> Priority: Critical
>
> I found serious problems with datanucleus code when using JDK7, resulting in
> some sort of exception being thrown when datanucleus code is entered.
> I tried source=1.7, target=1.7 with JDK7 as well as source=1.6, target=1.6
> with JDK7 and there was no visible difference in that the same unit tests
> failed.
> I tried upgrading datanucleus to 3.0.1, as per HIVE-2084.patch, which did not
> fix the failing tests.
> I tried upgrading datanucleus to 3.1-release, as per the advise of
> http://www.datanucleus.org/servlet/jira/browse/NUCENHANCER-86, which suggests
> using ASMv4 will allow datanucleus to work with JDK7. I was not successful
> with this either.
> I tried upgrading datanucleus to 3.1.2. I was not successful with this either.
> Regarding datanucleus support for JDK7+, there is the following JIRA
> http://www.datanucleus.org/servlet/jira/browse/NUCENHANCER-81
> which suggests that they don't plan to actively support JDK7+ bytecode any
> time soon.
> I also tested the following JVM parameters found on
> http://veerasundar.com/blog/2012/01/java-lang-verifyerror-expecting-a-stackmap-frame-at-branch-target-jdk-7/
> with no success either.
> This will become a more serious problem as people move to newer JVMs. If
> there are other who have solved this issue, please post how this was done.
> Otherwise, it is a topic that I would like to raise for discussion.
--
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
