Split the Kafka app into a binding module and a benchmark module - #25
Merged
estebanzimanyi merged 1 commit intoJul 23, 2026
Conversation
The kafka-streams-app module packed the generated MEOS binding surface and
the BerlinMOD streaming benchmark together, so a binding build/test dragged
in the 27-cell BerlinMOD matrix. Split it into a Maven reactor:
binding/ - the org.mobilitydb.meos.MeosOps* facades generated from the
JMEOS catalog + the generic Kafka Streams wiring layer + the
surface smoke tests. A pure projection; no application code.
benchmark/ - the berlinmod.* BerlinMOD Streams app + its tests, depending
on the binding module. All its MEOS access goes through the
binding's generated surface.
The parent pom drives both modules and shares the compiler/surefire config
(including the LD_LIBRARY_PATH for the native libmeos, now staged once at the
reactor root). build-jmeos.sh, the CI workflow and .gitignore follow the new
layout. The binding module now builds and tests on its own, without the
benchmark.
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.
The
kafka-streams-appmodule packs the generated MEOS binding surface and the BerlinMOD streaming benchmark into one module, so a binding build or test pulls in the 27-cell BerlinMOD matrix. This splits it into a Maven reactor:binding/— theorg.mobilitydb.meos.MeosOps*facades generated from the JMEOS catalog + the generic Kafka Streams wiring layer + the surface smoke tests. A pure projection of the MEOS surface; no application code.benchmark/— theberlinmod.*BerlinMOD Streams app + its tests, depending on the binding module. All its MEOS access goes through the binding's generated surface.The parent pom drives both modules and shares the compiler/surefire config, including the
LD_LIBRARY_PATHfor the native libmeos, now staged once at the reactor root.build-jmeos.sh, the CI workflow, and.gitignorefollow the new layout.The binding module now builds and tests on its own, without the benchmark — mirroring MobilitySpark, which is already a pure binding. Files move only; the Java is unchanged.