Share one JVM code generator across the bindings#40
Merged
estebanzimanyi merged 1 commit intoJul 16, 2026
Conversation
Introduce tools/codegen_jvm.py, the single MEOS-surface generator vendored
identically by every JVM binding, selected by --engine {spark|flink|kafka}.
The spark engine delegates verbatim to the existing tools/codegen_spark_udfs.py,
so the emitted UDF surface is byte-identical; the flink/kafka engines emit the
MeosOps* streaming facades. Wire the build to codegen_jvm.py --engine spark.
estebanzimanyi
force-pushed
the
jvmgen/unify-generator
branch
from
July 16, 2026 10:35
c62ed46 to
aa7f520
Compare
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.
Introduce
tools/codegen_jvm.py, a single MEOS-surface generator selected by--engine {spark|flink|kafka}and vendored identically by every JVM binding (MobilitySpark, MobilityFlink, MobilityKafka), so the generated surface cannot drift between engines.--engine sparkdelegates verbatim to the existingtools/codegen_spark_udfs.py(unchanged), so the emitted UDF surface is byte-identical to what that generator produces on its own (226 files,diff -rqclean).--engine flink|kafkaemit theMeosOps*streaming forwarder facades over the full jar surface (used by the Flink and Kafka bindings; not exercised here).The build invokes
codegen_jvm.py --engine spark;codegen_spark_udfs.pyremains the vendored spark back-end it delegates to.