hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
Date Sat, 20 Jul 2013 15:40:49 GMT


Hive QA commented on HIVE-3632:

{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 2646 tests passed

Test results:
Console output:

Executing org.apache.hive.ptest.execution.CleanupPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.
> Upgrade datanucleus to support JDK7
> -----------------------------------
>                 Key: HIVE-3632
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.9.1, 0.10.0, 0.11.0
>            Reporter: Chris Drome
>            Assignee: Xuefu Zhang
>            Priority: Critical
>             Fix For: 0.12.0
>         Attachments: HIVE-3632.1.patch, HIVE-3632.patch, HIVE-3632.patch.1
> 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,
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
> which suggests that they don't plan to actively support JDK7+ bytecode any time soon.
> I also tested the following JVM parameters found on
> 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.
> Test Properties:

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:

View raw message