-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Integration Test Failures for Databricks 13.3 Support #9646
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
Signed-off-by: Raza Jafri <[email protected]>
jlowe
reviewed
Nov 6, 2023
build |
jlowe
approved these changes
Nov 9, 2023
sameerz
added
the
task
Work required that improves the product but is not user facing
label
Nov 13, 2023
mythrocks
added a commit
to mythrocks/spark-rapids
that referenced
this pull request
Oct 24, 2024
Fixes NVIDIA#11528. This commit addresses the failure of `orc_test.py::test_project_fallback_when_reading_hive_fixed_length_char` when run on Databricks 13.3+. This test was skipped with an incorrect reason statement in NVIDIA#9646, to address a failure on Databricks 13.3. That failure was not the result of a data mismatch. It failed because the ProjectExec didn't fall back to CPU. (In fact, with Databricks 13.3 onwards, the ProjectExec is not involved in `SELECT *` queries.) As an aside, the same test is now skipped on Databricks 13.3 and 14.3, because the error condition it tests does not fire on those versions. Signed-off-by: MithunR <[email protected]>
mythrocks
added a commit
that referenced
this pull request
Nov 4, 2024
Fixes #11528. This commit addresses the failure of `orc_test.py::test_project_fallback_when_reading_hive_fixed_length_char` when run on Databricks 13.3+. This test was skipped with an incorrect reason statement in #9646, to address a failure on Databricks 13.3. That failure was not the result of a data mismatch. It failed because the ProjectExec didn't fall back to CPU. (In fact, with Databricks 13.3 onwards, the ProjectExec is not involved in `SELECT *` queries.) As an aside, the same test is now skipped on Databricks 13.3 and 14.3, because the error condition it tests does not fire on those versions. Signed-off-by: MithunR <[email protected]>
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.
This pull request fixes some of the integration test failures that were failing due to various reasons. The changes include adding PythonUDAF support to Databricks 13.3
Changes Made:
Tests
Fixes some of the failing tests. No new tests were added
Contributes towards 9175