Fix orc_write_test.py for [databricks] 14.3
#11664
Merged
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
Fixes NVIDIA#11529. This commit fixes the failure of `orc_write_test.py::test_orc_do_not_lowercase_columns` as described in NVIDIA#11529. The failure was the result of a change in the exception text in Databricks 14.3. (It differs from Spark 3.5, on which it is based, and more closely resembles Spark 4.0.) Signed-off-by: MithunR <[email protected]>
|
Build |
|
Sorting the test failure out now. Applying the patch on main seems to have messed up the imports, I think. |
Signed-off-by: MithunR <[email protected]>
|
Build |
revans2
approved these changes
Oct 28, 2024
|
Thank you for the review, @revans2. I've merged this change. |
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.
Fixes #11529.
This commit fixes the failure of
orc_write_test.py::test_orc_do_not_lowercase_columnsas described in #11529.The failure was the result of a change in the exception text in Databricks 14.3. (It differs from Spark 3.5, on which it is based, and more closely resembles Spark 4.0.)