Replies: 2 comments 2 replies
-
|
I would also be interested in this question but with SQL code. We use Sedona with DBT and rely on H3 grid to improve the performance. Having the ability to create an index like described for RDDs could probably bring an improvement on some big data applicaitons. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Apache Sedona Spatial Join via Spatial SQL uses distributed partitioning and spatial index automatically. Users don't need to specify anything. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
-
Docs say we need to broadcast the data to get spatial indexing with broadcast index join but this is a problem when the data is too large to fit in one node https://sedona.apache.org/latest/api/sql/Optimizer/?h=broadcast#broadcast-index-join
Any other way to trigger spatial indexing on the join? We can do this with RDD spatial partitioning and it works, but would like to preserve data frame API without converting back and forth from/to RDD.
Beta Was this translation helpful? Give feedback.
All reactions