Support spatialJoin when the join clause contains unequal conditions
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 784
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 58
Description
## Expected behavior
Support spatialJoin when the join clause contains unequal conditions
## Actual behavior
When there are spatial relationship conditions and non equivalence conditions in the join clause, spatialjoin is not effective and BroadcastNestedLoopJoin is used
## Steps to reproduce the problem
## Settings
Sedona version = 1.4.0
Apache Spark version = 3.3.0
Apache Flink version = ?
API type = Scala
Scala version = 2.12
JRE version = 1.8
Python version = ?
Environment = Standalone
Contributor guide
Research direction
Start by reproducing the Scala API case on Spark 3.3.0 with spatial relationship and non-equivalence conditions in the join clause. Inspect why the plan uses BroadcastNestedLoopJoin; the issue is done when spatialJoin remains effective for these unequal conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, scala, spark
- Domain
- data-engineering, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100