You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "David Mollitor (Jira)" <ji...@apache.org> on 2019/11/04 14:58:00 UTC

[jira] [Updated] (HIVE-22427) PersistenceManagerProvider Logs a Warning About datanucleus.autoStartMechanismMode

     [ https://issues.apache.org/jira/browse/HIVE-22427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Mollitor updated HIVE-22427:
----------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

Thanks [~abstractdog] for the review and [~mgergely] for getting this Jira into the right hands.  Committed to master.

> PersistenceManagerProvider Logs a Warning About datanucleus.autoStartMechanismMode
> ----------------------------------------------------------------------------------
>
>                 Key: HIVE-22427
>                 URL: https://issues.apache.org/jira/browse/HIVE-22427
>             Project: Hive
>          Issue Type: Improvement
>          Components: Standalone Metastore
>    Affects Versions: 3.2.0
>            Reporter: David Mollitor
>            Assignee: David Mollitor
>            Priority: Minor
>             Fix For: 4.0.0
>
>         Attachments: HIVE-22427.1.patch
>
>
> {code:none}
> WARN [pool-6-thread-2] metastore.PersistenceManagerProvider: datanucleus.autoStartMechanismMode is set to unsupported value null . Setting it to value: ignored
> {code}
> This does not need to be a WARN level logging for this scenario.  Perhaps if user configures the value to some non-null value, then emit a warning, otherwise, simply emit an INFO level stating that the configuration is not set and that a reasonable default value will be used.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)