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

Hive QA commented on HIVE-22427:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12984298/HIVE-22427.1.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 17546 tests passed

Test results: 
https://builds.apache.org/job/PreCommit-HIVE-Build/19209/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/19209/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-19209/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12984298 - PreCommit-HIVE-Build

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

Reply via email to