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

Hive QA commented on HIVE-22035:
--------------------------------



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

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

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

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

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: 12975545 - PreCommit-HIVE-Build

> HiveStrictManagedMigration settings do not always get set with --hiveconf 
> arguments
> -----------------------------------------------------------------------------------
>
>                 Key: HIVE-22035
>                 URL: https://issues.apache.org/jira/browse/HIVE-22035
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Jason Dere
>            Assignee: Jason Dere
>            Priority: Major
>         Attachments: HIVE-22035.1.patch
>
>
> Currently the --hiveconf arguments get added to the System properties. While 
> this allows official HiveConf variables to be set in the conf that is loaded 
> by the HiveStrictManagedMigration utility, there are utility-specific 
> configuration settings which we would want to be set from the command line. 
> For example since Ambari knows what the Hive system user name is it would 
> make sense to be able to set strict.managed.tables.migration.owner on the 
> command line when running this utility.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to