Avoid generating null filter values in test_delta_dfp_reuse_broadcast_exchange [databricks] #9745
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
…_exchange Signed-off-by: Jason Lowe <[email protected]>
jlowe
changed the title
|
build |
abellina
approved these changes
Nov 16, 2023
revans2
approved these changes
Nov 16, 2023
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.
After #9441 test_delta_dfp_reuse_broadcast_exchange can sometimes fail with a query analysis error like this:
The problem is that a query is run on the CPU to determine a filter value, but since the column of filter values can contain nulls, it's possible for the query to return None rather than an integer value. When "None" is plugged into the query template, it results in an invalid query.
This fixes the test to never generate nulls for the filter values.