[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719865#comment-13719865 ] Ashutosh Chauhan commented on HIVE-3632: +1 > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > 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.2.patch, HIVE-3632.3.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 > 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. > Test Properties: > CLEAR LIBRARY CACHE -- 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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[
https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719613#comment-13719613
]
Hive QA commented on HIVE-3632:
---
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12594065/HIVE-3632.3.patch
{color:green}SUCCESS:{color} +1 2651 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/180/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/180/console
Messages:
{noformat}
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
{noformat}
This message is automatically generated.
> Upgrade datanucleus to support JDK7
> ---
>
> Key: HIVE-3632
> URL: https://issues.apache.org/jira/browse/HIVE-3632
> 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.2.patch, HIVE-3632.3.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
> 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.
> Test Properties:
> CLEAR LIBRARY CACHE
--
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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[
https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719467#comment-13719467
]
Hive QA commented on HIVE-3632:
---
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12594065/HIVE-3632.3.patch
{color:green}SUCCESS:{color} +1 2651 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/178/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/178/console
Messages:
{noformat}
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
{noformat}
This message is automatically generated.
> Upgrade datanucleus to support JDK7
> ---
>
> Key: HIVE-3632
> URL: https://issues.apache.org/jira/browse/HIVE-3632
> 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.2.patch, HIVE-3632.3.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
> 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.
> Test Properties:
> CLEAR LIBRARY CACHE
--
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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[
https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718963#comment-13718963
]
Xuefu Zhang commented on HIVE-3632:
---
[~ashutoshc] Thanks for your comments.
0. Will base.
1. datanucleus.rdbms.useLegacyNativeValueStrategy is required because DN 3.x
changed the way that default values are generated. Without this, metastore
startup would fail while inserting default database entry. This is the error
msg:
{code}
javax.jdo.JDODataStoreException: Insert of object
"org.apache.hadoop.hive.metastore.model.MDatabase@176fbe79" using statement
"INSERT INTO `DBS` (`NAME`,`DESC`,`DB_LOCATION_URI`) VALUES (?,?,?)" failed :
Field 'DB_ID' doesn't have a default value
{code}
Setting this property to true instructs DN that the old way of generating
default values is used. More information can be found at
http://www.datanucleus.org/products/datanucleus/migration.html (search for
useLegacyNativeValueStrategy).
2. DN deps in ql/ivy.xml is probably not needed. My patch was originally based
on 0.10, where DN deps exist. I will test and remove if there is no need.
> Upgrade datanucleus to support JDK7
> ---
>
> Key: HIVE-3632
> URL: https://issues.apache.org/jira/browse/HIVE-3632
> 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
> 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.
> Test Properties:
> CLEAR LIBRARY CACHE
--
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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718946#comment-13718946 ] Xuefu Zhang commented on HIVE-3632: --- [~brocknoland] Yes, it's an ivy problem, which keeps the old DN libs while bringing new ones. > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > 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 > 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. > Test Properties: > CLEAR LIBRARY CACHE -- 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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[
https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13718907#comment-13718907
]
Ashutosh Chauhan commented on HIVE-3632:
[~xuefuz] Now that HIVE-4900 is in. Can you rebase this patch? Also few
comments:
* +
METASTORE_USE_LEGACY_VALUE_STRATEGY("datanucleus.rdbms.useLegacyNativeValueStrategy",
true), I don't know what this property does, can you briefly explain what it
is and why we need it for the upgrade ?
* Why we need to declare new deps in ql/ivy.xml Declaring them in
metastore/ivy.xml should suffice.
> Upgrade datanucleus to support JDK7
> ---
>
> Key: HIVE-3632
> URL: https://issues.apache.org/jira/browse/HIVE-3632
> 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
> 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.
> Test Properties:
> CLEAR LIBRARY CACHE
--
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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714593#comment-13714593 ] Brock Noland commented on HIVE-3632: These new libraries were causing most tests to fail. Until we finish this upgrade I have enabled deletion of the library cache on all builds. I assume this versioning issue with the libraries is an ivy problem? > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > 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 > 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. > Test Properties: > CLEAR LIBRARY CACHE -- 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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714470#comment-13714470 ] Xuefu Zhang commented on HIVE-3632: --- I think that's a good idea. It avoids confusions. Will do that. > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > 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 > 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. > Test Properties: > CLEAR LIBRARY CACHE -- 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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714463#comment-13714463 ] Edward Capriolo commented on HIVE-3632: --- Can we open a separate patch to fix the mapping file and trest and commit that first. > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > 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 > 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. > Test Properties: > CLEAR LIBRARY CACHE -- 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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[
https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714457#comment-13714457
]
Hive QA commented on HIVE-3632:
---
{color:green}Overall{color}: +1 all checks pass
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12593335/HIVE-3632.1.patch
{color:green}SUCCESS:{color} +1 2646 tests passed
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/111/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/111/console
Messages:
{noformat}
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
{noformat}
This message is automatically generated.
> Upgrade datanucleus to support JDK7
> ---
>
> Key: HIVE-3632
> URL: https://issues.apache.org/jira/browse/HIVE-3632
> 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
> 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.
> Test Properties:
> CLEAR LIBRARY CACHE
--
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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[
https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714427#comment-13714427
]
Hive QA commented on HIVE-3632:
---
{color:red}Overall{color}: -1 no tests executed
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12593335/HIVE-3632.1.patch
Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/110/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/110/console
Messages:
{noformat}
Executing org.apache.hive.ptest.execution.CleanupPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Tests failed with: InterruptedException: null
{noformat}
This message is automatically generated.
> Upgrade datanucleus to support JDK7
> ---
>
> Key: HIVE-3632
> URL: https://issues.apache.org/jira/browse/HIVE-3632
> 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
> 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.
> Test Properties:
> CLEAR LIBRARY CACHE
--
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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714184#comment-13714184 ] Xuefu Zhang commented on HIVE-3632: --- [~ashutoshc] My incomplete test shows that no upgrade script is necessary. The change of column names was to fix mistakes in DN mapping file (package.jdo) where a few columns weren't matched with the actually column names in schema. Old DN didn't catch those, and worked magically. Thus, the patch is to fix the field mapping rather than changing db schema. One of my test was to create DB schema using hive-schema-0.10.0.mysql.sql, and start metastore on the top of it. This patch works fine. I said my test is incomplete as it didn't try in case of metastore schema auto create. I don't think there will be a problem, but it's a good thing to check too. Otherwise, I don't think there is a need for schema upgrade. [~sergey.l.ivas...@intel.com] As to your question in RB, this patch doesn't change connection pooling in any form. The change you observed is a "missing" jar, which is part of DN-rdbms jar in the new DN version. Here is the DN doc for your reference. http://www.datanucleus.org/products/datanucleus/migration.html (search for datanucleus-connectionpool). I think Hive uses DBCP as a connection pool. > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > 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.patch > > > 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. > Test Properties: > CLEAR LIBRARY CACHE -- 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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714144#comment-13714144 ] Ashutosh Chauhan commented on HIVE-3632: [~xuefuz] Please tease out HIVE-4858 bits from the patch. It seems to me upgrade is required, we are changing column names. One way to test that is to create latest schema from script in metastore/scripts/upgrade/mysql in mysql, than apply your patch and than run tests against it. I will assume tests should fail because they wont find column names in mysql they are expecting. > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > 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.patch > > > 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. > Test Properties: > CLEAR LIBRARY CACHE -- 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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714091#comment-13714091 ] Sergey Shelukhin commented on HIVE-3632: 2 comments on RB > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > 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.patch > > > 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. > Test Properties: > CLEAR LIBRARY CACHE -- 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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713705#comment-13713705 ] Brock Noland commented on HIVE-3632: [~xuefuz] shoot, we support that internally via the kickout shell script. I haven't built that support for that yet because we have a client server model as opposed to directly invoking ptest2. I'll look at it today. > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > 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.patch > > > 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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713324#comment-13713324 ] Xuefu Zhang commented on HIVE-3632: --- I believe these failures were caused by mismatched DN libraries. We need to either do a "ant very-clean" or remove ivy cache before launching the build. Or both. > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > 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.patch > > > 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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[
https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713300#comment-13713300
]
Hive QA commented on HIVE-3632:
---
{color:red}Overall{color}: -1 build exited with an error
Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12593080/HIVE-3632.patch
{color:red}ERROR:{color} -1 due to 254 failed/errored test(s)
Failed tests:
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testSimpleTypeApi
org.apache.hadoop.hive.jdbc.TestJdbcDriver.testDriverProperties
org.apache.hadoop.hive.service.TestHiveServerSessions.testSessionVars
org.apache.hadoop.hive.ql.metadata.TestHiveMetaStoreChecker.testTableCheck
org.apache.hadoop.hive.metastore.TestEmbeddedHiveMetaStore.testSimpleTable
org.apache.hadoop.hive.service.TestHiveServer.testDynamicSerde
org.apache.hadoop.hive.ql.parse.TestParseNegative.testParseNegative_unknown_column4
org.apache.hadoop.hive.metastore.TestSetUGIOnOnlyServer.testColumnStatistics
org.apache.hadoop.hive.cli.TestHBaseCliDriver.testCliDriver_hbase_stats2
org.apache.hadoop.hive.jdbc.TestJdbcDriver.testDatabaseMetaData
org.apache.hadoop.hive.ql.metadata.TestHive.testPartition
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testAlterPartition
org.apache.hadoop.hive.metastore.TestMetaStoreInitListener.testMetaStoreInitListener
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStoreIpAddress.testIpAddress
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testFilterSinglePartition
org.apache.hadoop.hive.metastore.TestSetUGIOnOnlyClient.testAlterTable
org.apache.hadoop.hive.metastore.TestEmbeddedHiveMetaStore.testConcurrentMetastores
org.apache.hadoop.hive.ql.metadata.TestHive.testGetAndDropTables
org.apache.hadoop.hive.cli.TestHBaseCliDriver.testCliDriver_hbase_joins
org.apache.hadoop.hive.ql.history.TestHiveHistory.testQueryloglocParentDirNotExist
junit.framework.TestSuite.org.apache.hive.service.cli.TestEmbeddedThriftCLIService
org.apache.hadoop.hive.metastore.TestSetUGIOnOnlyClient.testPartition
org.apache.hadoop.hive.ql.metadata.TestHiveRemote.testIndex
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testGetConfigValue
org.apache.hadoop.hive.jdbc.TestJdbcDriver.testSelectAllFetchSize
org.apache.hadoop.hive.ql.metadata.TestHive.testThriftTable
org.apache.hadoop.hive.metastore.TestSetUGIOnOnlyServer.testAlterTable
org.apache.hadoop.hive.metastore.TestSetUGIOnOnlyClient.testColumnStatistics
org.apache.hadoop.hive.ql.parse.TestParseNegative.testParseNegative_nonkey_groupby
org.apache.hadoop.hive.cli.TestHBaseCliDriver.testCliDriver_hbase_scan_params
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testRenamePartition
org.apache.hadoop.hive.ql.parse.TestParseNegative.testParseNegative_missing_overwrite
org.apache.hadoop.hive.metastore.TestMetaStoreAuthorization.testMetaStoreAuthorization
org.apache.hadoop.hive.ql.parse.TestParseNegative.testParseNegative_wrong_distinct1
org.apache.hadoop.hive.ql.parse.TestParseNegative.testParseNegative_unknown_column1
org.apache.hadoop.hive.ql.parse.TestParseNegative.testParseNegative_unknown_function4
org.apache.hadoop.hive.metastore.TestSetUGIOnOnlyServer.testDatabaseLocation
org.apache.hadoop.hive.cli.TestHBaseCliDriver.testCliDriver_hbase_stats
org.apache.hadoop.hive.metastore.TestEmbeddedHiveMetaStore.testAlterPartition
org.apache.hadoop.hive.jdbc.TestJdbcDriver.testSelectAllMaxRows
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testPartition
org.apache.hadoop.hive.metastore.TestSetUGIOnOnlyServer.testSimpleTypeApi
org.apache.hadoop.hive.metastore.TestSetUGIOnOnlyServer.testSimpleTable
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testNameMethods
org.apache.hadoop.hive.service.TestHiveServer.testNonHiveCommand
org.apache.hadoop.hive.jdbc.TestJdbcDriver.testErrorMessages
org.apache.hadoop.hive.ql.parse.TestParseNegative.testParseNegative_invalid_map_index
org.apache.hadoop.hive.cli.TestHBaseCliDriver.testCliDriver_hbase_ppd_key_range
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testPartitionFilter
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testFilterSinglePartition
org.apache.hadoop.hive.metastore.TestSetUGIOnOnlyClient.testAlterViewParititon
org.apache.hadoop.hive.jdbc.TestJdbcDriver.testSelectAll
org.apache.hadoop.hive.metastore.TestSetUGIOnOnlyServer.testDatabase
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testColumnStatistics
org.apache.hadoop.hive.ql.metadata.TestSemanticAnalyzerHookLoading.testHookLoading
org.apache.hadoop.hive.ql.parse.TestParseNegative.testParseNegative_unknown_table1
org.apache.hadoop.hive.metastore.TestRemoteHiveMetaStore.testComplexTable
org.apache.hadoop.hive.metastore.TestSetUGIOnBothClientServer.testColumnStatistics
org.apache.hadoop.hive.service.TestHiveServer.testAddFileShouldFailIfFileNotExist
org.apache.hadoop.hive.metastore.TestH
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713036#comment-13713036 ] Xuefu Zhang commented on HIVE-3632: --- Review board: https://reviews.apache.org/r/12750/ > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > 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.patch > > > 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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708673#comment-13708673 ] Ashutosh Chauhan commented on HIVE-3632: I am all for updating DN. Huge +1 But we need to be wary of https://issues.apache.org/jira/browse/HIVE-2084?focusedCommentId=13014240&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13014240 Feels like we might need to provide upgrade scripts for folks to migrate because of this. > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > Project: Hive > Issue Type: Bug > Components: Metastore >Affects Versions: 0.9.1, 0.10.0 >Reporter: Chris Drome >Assignee: Xuefu Zhang >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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708637#comment-13708637 ] Xuefu Zhang commented on HIVE-3632: --- Since nobody is working on this, I will give it a shot. > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > Project: Hive > Issue Type: Bug > Components: Metastore >Affects Versions: 0.9.1, 0.10.0 >Reporter: Chris Drome >Assignee: Xuefu Zhang >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
[jira] [Commented] (HIVE-3632) Upgrade datanucleus to support JDK7
[ https://issues.apache.org/jira/browse/HIVE-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708639#comment-13708639 ] Xuefu Zhang commented on HIVE-3632: --- To compile and run hive on JDK7, DataNucleus needs to be upgraded. The current plan is to upgrade using the following library versions: datanucleus-api-jdo-3.2.1.jar datanucleus-rdbms-3.2.1.jar datanucleus-core-3.2.2.jar. These versions work for both JDK6 and JDK7. After upgrade, there is only a few test failures with JDK6. Besides the unit tests, more tests will be conducted. This is related to HIVE-2084, but the goal here is slightly different. Of course, the upgrade needs to address all issues that may arise. > Upgrade datanucleus to support JDK7 > --- > > Key: HIVE-3632 > URL: https://issues.apache.org/jira/browse/HIVE-3632 > Project: Hive > Issue Type: Bug > Components: Metastore >Affects Versions: 0.9.1, 0.10.0 >Reporter: Chris Drome >Assignee: Xuefu Zhang >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
