Skip to content

refactor: rename vortex-geo to vortex-spatial - #9284

Merged
gatesn merged 3 commits into
developfrom
codex/vortex-spatial-rename
Aug 7, 2026
Merged

refactor: rename vortex-geo to vortex-spatial#9284
gatesn merged 3 commits into
developfrom
codex/vortex-spatial-rename

Conversation

@HarukiMoriarty

@HarukiMoriarty HarukiMoriarty commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Rationale

Use spatial consistently for Vortex-owned APIs and identifiers, while reserving Geo terminology for external standards and crates such as GeoArrow, GeoParquet, geo-types, and geo-traits.

What changes are included?

  • Rename the crate and Rust module from vortex-geo / vortex_geo to vortex-spatial / vortex_spatial.
  • Rename Vortex extension IDs from vortex.geo.* to vortex.st.*.
  • Rename public metadata, scalar-function, pruning, and session APIs to Spatial* names.
  • Update DuckDB, JNI, benchmark, workflow, documentation, comments, and tests.
  • Rename the SpatialBench native lane to vortex-spatial-native and document the default, native, and three-way benchmark commands.
  • Keep GeoArrow, GeoParquet, geo-types, and geo-traits names where they describe external interfaces.

User-facing changes

This is a breaking rename for the spatial crate, Rust imports, extension IDs, and Spatial* APIs. Spatial predicate semantics and storage behavior are unchanged.

Rename the Vortex-owned spatial crate, extension IDs, APIs, DuckDB integration, and benchmark lane from geo terminology to spatial terminology. Keep GeoArrow, GeoParquet, and geo-types names where they refer to external standards or crates.

Signed-off-by: Nemo Yu <zyu379@wisc.edu>
@HarukiMoriarty HarukiMoriarty added the changelog/break A breaking API change label Aug 7, 2026
@HarukiMoriarty
HarukiMoriarty requested a review from gatesn August 7, 2026 16:47
Signed-off-by: Nemo Yu <zyu379@wisc.edu>
@codspeed-hq

codspeed-hq Bot commented Aug 7, 2026

Copy link
Copy Markdown

Merging this PR will improve performance by 18.78%

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⚡ 2 improved benchmarks
✅ 1944 untouched benchmarks
🆕 34 new benchmarks
⏩ 42 skipped benchmarks1

Performance Changes

Mode Benchmark BASE HEAD Efficiency
Simulation decompress[u32, (10000, 256)] 100.4 µs 83.9 µs +19.71%
Simulation cold_misaligned[(64, 256)] 5.1 ms 4.4 ms +17.85%
🆕 Simulation column_x_column_points N/A 470.4 µs N/A
🆕 Simulation column_x_column_polygons N/A 650.6 µs N/A
🆕 Simulation constant_x_nullable_points N/A 1.5 ms N/A
🆕 Simulation constant_x_nullable_polygons_disjoint N/A 1.7 ms N/A
🆕 Simulation constant_x_points N/A 1.4 ms N/A
🆕 Simulation constant_x_polygons_disjoint N/A 1.5 ms N/A
🆕 Simulation nullable_polygons_90pct_x_constant_point N/A 588.7 µs N/A
🆕 Simulation nullable_polygons_x_nullable_points N/A 702.7 µs N/A
🆕 Simulation polygons_x_constant_point N/A 467.4 µs N/A
🆕 Simulation column_x_column_polygons N/A 623 µs N/A
🆕 Simulation nullable_points_x_constant N/A 1.5 ms N/A
🆕 Simulation nullable_polygons_disjoint_x_constant N/A 1.8 ms N/A
🆕 Simulation points_x_constant N/A 1.4 ms N/A
🆕 Simulation polygons_disjoint_x_constant N/A 1.5 ms N/A
🆕 Simulation polygons_overlapping_x_constant N/A 1.4 ms N/A
🆕 Simulation nullable_point_column_x_constant_point N/A 753.6 µs N/A
🆕 Simulation point_column_x_constant_point N/A 559.1 µs N/A
🆕 Simulation point_column_x_point_column N/A 731.4 µs N/A
... ... ... ... ... ...

ℹ️ Only the first 20 benchmarks are displayed. Go to the app to view all benchmarks.

Tip

Curious why this is faster? Comment @codspeedbot explain why this is faster on this PR, or directly use the CodSpeed MCP with your agent.


Comparing codex/vortex-spatial-rename (e2863b5) with develop (66c447e)

Open in CodSpeed

Footnotes

  1. 42 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@gatesn
gatesn enabled auto-merge (squash) August 7, 2026 17:09
@gatesn
gatesn merged commit fed7038 into develop Aug 7, 2026
81 checks passed
@gatesn
gatesn deleted the codex/vortex-spatial-rename branch August 7, 2026 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog/break A breaking API change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants