[
https://issues.apache.org/jira/browse/HIVE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539634#comment-13539634
]
Deepesh Khandelwal commented on HIVE-2084:
------------------------------------------
After upgrading the datanucleus I ran into the runtime exception FCOMMENT
invalid column name in COLUMNS_V2, this happens only when hive schema is
pre-created with the upgrade SQL scripts (i.e.
datanucleus.autoCreateSchema=false). So on MySQL, the workaround was to start
with a blank schema and set datanucleus.autoCreateSchema=true but this turned
out to be a problem on Oracle as the automatic creation of schema fails for the
table TBLS (see HIVE-2928). To get around this on Oracle I pre-created the
table TBLS and couple of other datanucleus tables (SEQUENCE_TABLE &
NUCLEUS_TABLES) and let the server automatically create the other missing
tables. If required, I can attach the patch for the SQL script I used for
Oracle.
> Upgrade datanucleus from 2.0.3 to 3.0.1
> ---------------------------------------
>
> Key: HIVE-2084
> URL: https://issues.apache.org/jira/browse/HIVE-2084
> Project: Hive
> Issue Type: Improvement
> Components: Metastore
> Reporter: Ning Zhang
> Assignee: Sushanth Sowmyan
> Labels: datanucleus
> Attachments: ASF.LICENSE.NOT.GRANTED--HIVE-2084.D2397.1.patch,
> HIVE-2084.1.patch.txt, HIVE-2084.2.patch.txt, HIVE-2084.D5685.1.patch,
> HIVE-2084.patch
>
>
> It seems the datanucleus 2.2.3 does a better join in caching. The time it
> takes to get the same set of partition objects takes about 1/4 of the time it
> took for the first time. While with 2.0.3, it took almost the same amount of
> time in the second execution. We should retest the test case mentioned in
> HIVE-1853, HIVE-1862.
--
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
