Explicitly set table props to accommodate for different defaults [databricks] #11970
+6
−7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gerashegalov
changed the title
gerashegalov
changed the title
Signed-off-by: Gera Shegalov <[email protected]>
Signed-off-by: Gera Shegalov <[email protected]>
|
build |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses #11541
Table properties should be set unconditionally to accommodate diverging defaults in different Databricks versions
Improves
env TEST_PARALLEL=0 \ TEST_MODE=DELTA_LAKE_ONLY TESTS=delta_lake_update_test.py \ PYSP_TEST_spark_rapids_sql_detectDeltaLogQueries=false \ PYSP_TEST_spark_rapids_sql_format_parquet_reader_type=PERFILE \ ./jenkins/databricks/test.sh