You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Andy Jefferson (JIRA)" <ji...@apache.org> on 2012/07/16 08:52:35 UTC

[jira] [Commented] (HIVE-2084) Upgrade datanucleus from 2.0.3 to 3.0.1

    [ https://issues.apache.org/jira/browse/HIVE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414882#comment-13414882 ] 

Andy Jefferson commented on HIVE-2084:
--------------------------------------

No idea what your "table not found" problem is, but if this is at startup logic would suggest passing all classes to DataNucleus via an auto-start mechanism, or using a persistence.xml. If using persistence.xml then make sure you also have persistence property "datanucleus.PersistenceUnitLoadClasses" set to true. That way, all classes are known about once started, and the store knows about these classes too (hence knows of their tables). There are no outstanding issues reported around tables not being found, so if you have something then you need to generate a reproduceable testcase and report it.

DataNucleus 2.x versions haven't been supported for some time. DataNucleus 3.0 is now not being updated (except for commercial requests), since DataNucleus 3.1 will be out in < 2 weeks.
                
> 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: HIVE-2084.1.patch.txt, HIVE-2084.2.patch.txt, HIVE-2084.D2397.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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira