[ https://issues.apache.org/jira/browse/HIVE-22035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891312#comment-16891312 ]
Ashutosh Chauhan commented on HIVE-22035: ----------------------------------------- +1 > 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)