Skip to content

Add the MobilitySpark pin manifest and per-binding generator policy#29

Open
estebanzimanyi wants to merge 1 commit into
MobilityDB:mainfrom
estebanzimanyi:tooling/canonical-generator-policy
Open

Add the MobilitySpark pin manifest and per-binding generator policy#29
estebanzimanyi wants to merge 1 commit into
MobilityDB:mainfrom
estebanzimanyi:tooling/canonical-generator-policy

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

What

Brings MobilitySpark onto the ecosystem-wide per-binding generator policy (same treatment as JMEOS #29, GoMEOS #6, MEOS.NET #6, meos-rs #4, PyMEOS #96/#21, MobilityDuck #206):

Docs + manifest only — no code, no build impact.

Add tools/pin/compose-order.txt (the canonical fold manifest; MobilityDB#28 generated
dispatch on the MobilityDB#27 generator) and GENERATION.md (the per-binding generator
policy: MobilitySpark binds the JMEOS jar and generates its Spark UDF surface
via tools/codegen_spark_udfs.py, retiring the hand UDFs generate-then-retire).
@estebanzimanyi estebanzimanyi force-pushed the tooling/canonical-generator-policy branch from d8f784d to 9cd0be1 Compare June 25, 2026 21:39
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