[
https://issues.apache.org/jira/browse/HIVE-23612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136278#comment-17136278
]
Jason Dere commented on HIVE-23612:
-----------------------------------
I think this looks good. One suggestion - rather than hardcoding "hive" as the
default owner in these changes, there is a setting
"strict.managed.tables.migration.owner" that is used for the managed table
owner .. you could use a similar setting
"strict.external.tables.migration.owner" for this "unowned" tables user, with a
default value of "hive".
> Option for HiveStrictManagedMigration to impersonate a user for FS operations
> -----------------------------------------------------------------------------
>
> Key: HIVE-23612
> URL: https://issues.apache.org/jira/browse/HIVE-23612
> Project: Hive
> Issue Type: Improvement
> Reporter: Ádám Szita
> Assignee: Ádám Szita
> Priority: Major
> Attachments: HIVE-23612.0.patch, HIVE-23612.1.patch
>
>
> HiveStrictManagedMigration tool can be used to move HDFS paths and to change
> ownership on said paths. It may be beneficial to do such file system
> operations as a different user than the one the tool itself is run.
> Moreover, while creating the external DB directory, the tool will chown the
> new directory to the user set as DB owner in HMS. If this is unset, no chown
> command is used. In this case we should make the 'hive' user the directory
> owner.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
