Split the Flink app into a binding module and a benchmark module - #48
Merged
estebanzimanyi merged 1 commit intoJul 23, 2026
Conversation
The flink-processor module packed the generated MEOS binding surface and
four streaming benchmark/demo apps (berlinmod, aisdata, sncbdata, sedona)
into one module, so a binding build/test pulled all of them in. Split it
into a Maven reactor:
binding/ - the org.mobilitydb.meos.MeosOps* facades generated from the
JMEOS catalog + the generic Flink DataStream wiring layer +
the surface smoke tests. A pure projection; no application
code. Its dependencies are only what the wirings and smokes
import (flink-streaming/core/clients, jnr, jmeos).
benchmark/ - the berlinmod/aisdata/sncbdata/sedona apps + their tests and
run scripts, depending on the binding module. It keeps the
table API, kafka connector, jts, jackson, log4j, postgresql
and the sedona profile, and the flink-kafka2postgres jar name.
The parent pom drives both modules and shares the compiler/surefire config
(including LD_LIBRARY_PATH for libmeos from meos.lib.dir). The CI workflow
and .gitignore follow the new layout. The binding module now builds and
tests on its own, without the benchmarks.
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
flink-processormodule packs the generated MEOS binding surface and four streaming benchmark/demo apps (berlinmod,aisdata,sncbdata,sedona) into one module, so a binding build or test pulls all of them in. This splits it into a Maven reactor:binding/— theorg.mobilitydb.meos.MeosOps*facades generated from the JMEOS catalog + the generic Flink DataStream wiring layer + the surface smoke tests. A pure projection of the MEOS surface; no application code. Its dependencies are only what the wirings and smokes import (flink-streaming/core/clients, jnr, jmeos).benchmark/— theberlinmod/aisdata/sncbdata/sedonaapps + their tests and run scripts, depending on the binding module. It keeps the table API, kafka connector, jts, jackson, log4j, postgresql and thesedonaprofile, and theflink-kafka2postgresjar name the run scripts and Dockerfiles launch.The parent pom drives both modules and shares the compiler/surefire config, including
LD_LIBRARY_PATHfor libmeos frommeos.lib.dir. The CI workflow and.gitignorefollow the new layout.The binding module builds and tests on its own, without the benchmarks — the same pure-binding shape MobilitySpark already has. Files move only; the Java is unchanged.