Skip to content

Recognize MobilitySpark as a peer SQL surface#6

Open
estebanzimanyi wants to merge 3 commits into
MobilityDB:mainfrom
estebanzimanyi:readme/three-platform-parity
Open

Recognize MobilitySpark as a peer SQL surface#6
estebanzimanyi wants to merge 3 commits into
MobilityDB:mainfrom
estebanzimanyi:readme/three-platform-parity

Conversation

@estebanzimanyi
Copy link
Copy Markdown
Member

The Spark plugin now carries the same MEOS-backed type system, function catalog, and BerlinMOD reference queries that the PostgreSQL and DuckDB peers carry. The README is updated to reflect three SQL surfaces with portable SQL parity, and MobilityPySpark is reframed as the PySpark entry point to MobilitySpark rather than a separate application platform.

…d MobilityDuck

The Spark plugin now carries the same MEOS-backed type system, function catalog, and BerlinMOD reference queries that the PostgreSQL and DuckDB peers carry. The README is updated to reflect three SQL surfaces with portable SQL parity, and MobilityPySpark is reframed as the PySpark entry point to MobilitySpark rather than a separate application platform.
…dataset description

BerlinMOD-Hanoi adapts the BerlinMOD generator to Hanoi OSM data and uses MobilityDB-BerlinMOD as a submodule, so it belongs as a city instantiation of the same row rather than a peer dataset. MobilityDB-Brussels is real Brussels public-transport data (STIB, TLC), not a BerlinMOD instantiation; the row description is sharpened to make the distinction explicit.
The repository is currently private and should not be linked from a public org README. The row is removed; if and when the repo goes public the row can be reintroduced.
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.

1 participant