Validate SQL elements before making changes to the Cluster #168
Assignees
Labels
Comments
|
That would be a good place to incorporate issue-167 to test also the execution engine (tez as example) configs the users set wia -po[l|r] - #167 |
dstreev
added a commit
to dstreev/hms-mirror
that referenced
this issue
Jan 24, 2025
BETA Iceberg conversion support for the STORAGE_MIGRATION data strategy. See [Iceberg Conversion](hms-mirror-iceberg_migration.md) for more details. **Bugs (Fixed)** [Add to connection init the ability to set the queue AND trigger an engine resource](cloudera-labs/hms-mirror#173) [cloudera-labs/hms-mirror#168 Validate SQL elements before making changes to the Cluster](cloudera-labs/hms-mirror#168) [Extend the HS2 connection validation with Tez task validation](cloudera-labs/hms-mirror#167) [The reset-to-default-location doesn't seem to be working in v2](cloudera-labs/hms-mirror#165)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If there are SQL statements that may not be 'allowed' under the current configuration, stop the process 'before' any changes are made to the cluster.
EG: If the user has NOT whitelisted a hive environment setting like
tez.grouping.max-sizeand it will cause issues, expose this and abate the run before it starts.The text was updated successfully, but these errors were encountered: