Skip to content

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

Merged
estebanzimanyi merged 1 commit into
MobilityDB:mainfrom
estebanzimanyi:tooling/canonical-generator-policy
Jul 8, 2026
Merged

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

Conversation

@estebanzimanyi

@estebanzimanyi estebanzimanyi commented Jun 25, 2026

Copy link
Copy Markdown
Member

What

Adds the per-binding generator policy for MobilitySpark:

  • tools/pin/compose-order.txt — the dependency-ordered fold manifest (generator → generated dispatch; benchmark; doc).
  • GENERATION.md — the policy. MobilitySpark is a consumer binding: it binds the JMEOS jar (not MEOS-API directly), and its generator tools/codegen_spark_udfs.py mirrors the JMEOS FunctionsGenerator and emits the Spark UDF layer by @ingroup. The end state of the UDF layer is registerAll().

Docs and 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
@estebanzimanyi estebanzimanyi merged commit c7d5987 into MobilityDB:main Jul 8, 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.

1 participant