[
https://issues.apache.org/jira/browse/HIVE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463271#comment-13463271
]
Sushanth Sowmyan commented on HIVE-2084:
----------------------------------------
Andy, thanks for the pointer, I'll try to see what's different about our use of
Maps.
I've rebased and updated the patch, but unfortunately, I'm not entirely
conversant with phabricator yet, and wound up creating a new "review" while
updating. It's now up on https://reviews.facebook.net/D5685
The easiest way to test out the difference I allude to is to run the following
with and without this patch:
{noformat}
ant clean && ant very-clean && ant package && ant test -Dtestcase=TestCliDriver
-Dtest.silent=false -Dqfile=alter_index.q
{noformat}
If I dig through the stack trace with prints, the eventual error that's thrown
now has an error code of 056063, which localization-maps to "Null values not
allowed in persistent maps."
> 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
