Disable test_broadcast_nested_loop_join_condition_missing_count on Databricks #3246
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.
Relates to #3244
The new test_broadcast_nested_loop_join_condition_missing_count test is failing due to what appears to be a bug in hash aggregate code. It looks like we're trying to pull out an input reference from a batch that has no columns. Thus this looks more like a latent bug in hash aggregate on Databricks that was exposed in by the new join code rather than a bug in the new join code itself.
To unblock the build while more investigation into the hash aggregate issue occurs, this xfails the test on Databricks and references #3244.