[SEDONA-262] Don't optimize equi-join by default, add an option to configure when to optimize spatial joins #797
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
Kontinuation
force-pushed
the
prefer-equi-join
branch
from
21cd779
to
2a26529
Compare
…donaConf to control the behavior of spatial join optimizer.
Kontinuation
force-pushed
the
prefer-equi-join
branch
from
2a26529
to
543e1b7
Compare
jiayuasu
approved these changes
Mar 13, 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.
Did you read the Contributor Guide?
Is this PR related to a JIRA ticket?
[SEDONA-XXX] my subject.What changes were proposed in this PR?
This patch disabled Sedona spatial join optimizations on equi-joins by default. User can still switch to the old behavior with
spark.conf.set("sedona.join.optimizationmode", "all"). Please refer to the JIRA ticket for details about this patch.How was this patch tested?
Added tests with various
"sedona.join.optimizationmode"options and verified that join queries are producing expected executed plans.Did this PR include necessary documentation updates?