Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
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.