Hunter Logan created KUDU-3231:
----------------------------------
Summary: Kudu HMS tool should check user perms
Key: KUDU-3231
URL: https://issues.apache.org/jira/browse/KUDU-3231
Project: Kudu
Issue Type: Improvement
Components: CLI
Reporter: Hunter Logan
If a user runs "kudu hms fix <kudu-masters> -drop_orphan_hms_tables" from a
profile that has perms to read the tables in HMS but not in Kudu, the script
will consider all tables missing the Kudu information to be orphaned and drop
them. This can occur even as the Kudu user if the environment has Sentry.
It would be nice if the script warned about this, and/or required a "–force"
argument if the user wishes to proceed. At the very least the script should
probably be sure that it is being run as the Kudu user.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
