Skip to content

feat(rust/sedona-spatial-join) Making SpatialIndex a trait#645

Open
pwrliang wants to merge 3 commits intoapache:mainfrom
pwrliang:spatial-index-trait
Open

feat(rust/sedona-spatial-join) Making SpatialIndex a trait#645
pwrliang wants to merge 3 commits intoapache:mainfrom
pwrliang:spatial-index-trait

Conversation

@pwrliang
Copy link
Contributor

This PR splits SpatialIndex into a SpatialIndex trait and a default implementation DefaultSpatialIndex. These changes are for the upcoming GPU-based spatial join.

@pwrliang pwrliang force-pushed the spatial-index-trait branch from dcab75a to 085a047 Compare February 19, 2026 22:43
Copy link
Member

@Kontinuation Kontinuation left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The refactoring for SpatialIndex looks good to me. BTW, I believe that SpatialIndexBuilder also need to be a trait.

self.probe_threads_counter.fetch_sub(1, Ordering::Relaxed) == 1
}

fn report_probe_completed(&self) -> bool;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can do another pass of refactoring to move probe completion markers out of spatial index, this will simplify the interface of SpatialIndex. This does not need to be done in this PR.

@paleolimbot
Copy link
Member

Thank you for opening!

I'm happy to take a look after the 0.3.0 release branch is created (hopefully Monday!).

@pwrliang pwrliang changed the title Making SpatialIndex a trait feat(rust/sedona-spatial-join) Making SpatialIndex a trait Feb 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants