Add the MobilityKafka pin manifest and per-binding generator policy - #17
Closed
estebanzimanyi wants to merge 1 commit into
Closed
Add the MobilityKafka pin manifest and per-binding generator policy#17estebanzimanyi wants to merge 1 commit into
estebanzimanyi wants to merge 1 commit into
Conversation
Add tools/pin/compose-order.txt (records the topology gap: 0 open PRs to main; the MEOS consumer + facade generator live on the fork branch consolidate/kafka-benchmark and need a base=main PR) and GENERATION.md (the per-binding generator policy: MobilityKafka binds the JMEOS jar and generates the org.mobilitydb.meos facades via tools/codegen_facades.py).
estebanzimanyi
force-pushed
the
tooling/canonical-generator-policy
branch
from
June 25, 2026 21:40
6aace13 to
85c94e6
Compare
Member
Author
|
Closing: this predates the move off the ecosystem-pin model. It adds tools/pin/compose-order.txt and tools/regen-from-pin.sh (the pin/compose-order machinery, since retired across the bindings) plus a GENERATION.md written around pinning that describes a generator (tools/codegen_facades.py), a jar builder (build-jmeos.sh), and an app (kafka-streams-app) not present on main. The generated MEOS operator layer and its GENERATION.md will land together in the change that brings the generated Kafka Streams consumer to main. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Brings MobilityKafka 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, MobilitySpark #29, MobilityFlink #32):
tools/pin/compose-order.txt— records that MobilityKafka has 0 open PRs to main and the topology gap: the MEOS streaming consumer + the facade generator (tools/codegen_facades.py) live on the fork branchconsolidate/kafka-benchmarkand need abase=mainPR.GENERATION.md— the policy: MobilityKafka is a consumer binding (binds the JMEOS jar viabuild-jmeos.sh); its generatortools/codegen_facades.py(the same as MobilityFlink) emits theorg.mobilitydb.meos.MeosOps*facades thekafka-streams-appconsumes.Docs + manifest only — no code, no build impact.