[jira] [Commented] (HIVE-3521) Concurrent metastore calls provoke Datanucleus IllegalStateException: "Table object has not been been initialised"

["Andy Jefferson (JIRA)" <ji...@apache.org>]

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

Andy Jefferson commented on HIVE-3521:
--------------------------------------

I've never seen it, and that private company running that proprietary benchmark (for their proprietary product) didn't bother configuring DataNucleus (surprising?). 
Use of the DN persistence property "datanucleus.PersistenceUnitLoadClasses" at startup together with a persistence-unit, or alternatively use of an auto-start mechanism, as well as locking of your PMF/EMF until it was initialised would clearly mean that the internal schema was initialised. You seem to be executing a query and it is still discovering classes that map to your schema; not a good way of running
                
> Concurrent metastore calls provoke Datanucleus IllegalStateException: "Table object has not been been initialised"
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-3521
>                 URL: https://issues.apache.org/jira/browse/HIVE-3521
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 0.9.0
>            Reporter: Carl Steinbach
>


--
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