Closed SvampX closed 4 weeks ago
As per described in extracting and cleaning methods possible issues we might try different way to read and store TBLPROPERTIES. Partially it was done on the view side here https://github.com/liquibase/liquibase-databricks/blob/main/src/main/java/liquibase/ext/databricks/snapshot/jvm/ViewSnapshotGeneratorDatabricks.java#L81-L89 I suggest storing in the https://github.com/liquibase/liquibase-databricks/blob/main/src/main/java/liquibase/ext/databricks/change/createTable/ExtendedTableProperties.java tblProperties parameter as a Map, not a raw String. This would make easier and fail proof cleaning up of system table properties and parsing needed stored there data.
Are we writing tests for this PR?
Are we writing tests for this PR? @suryaaki2 so far for Databricks we are only adding new test cases for test harness, as in
createClusteredTableNew.*
files added in this PR.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
Tested following liquibase commands:
Changelog generates with present CLUSTER BY part with appropriate columns. Tested case with 1 and 2 clustering columns. Generated changeset example: