Track upstream master for the MEOS derivation#42
Merged
estebanzimanyi merged 1 commit intoJul 16, 2026
Merged
Conversation
Derive the whole surface from MobilityDB master in CI instead of a pinned commit plus a committed JMEOS jar, mirroring the Spark reference: - provision-meos runs with mobilitydb-ref: master, so the catalog and the all-families libmeos come from master. - The streaming-relevance baseline is derived from that catalog in CI (tools/regen_baseline.sh) and gitignored, not committed. - The JMEOS jar is built from JMEOS main against the same catalog + libmeos and installed as org.jmeos:meos:1.0; flink-processor depends on those coordinates and the facade generator reads that jar, replacing the committed system-scoped flink-processor/jar/JMEOS.jar. The jar surface, the generated facades and the libmeos the smoke tests load now all track master together, so the facades can no longer drift from the surface they are built against. Drop tools/meos-source-commit.txt. regen_baseline.sh creates its output directory, since the baseline is a gitignored build artifact absent from a fresh checkout.
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.
Mirrors the Spark reference: the whole surface derives from MobilityDB master in CI, with no pinned commit and no committed JMEOS jar.
What changes
provision-meosruns withmobilitydb-ref: master— the catalog and the all-familieslibmeos.socome from master.tools/regen_baseline.sh) and gitignored, not committed. The classifier is deterministic, so the baseline tracks master by construction.mainagainst the same catalog + libmeos and installed asorg.jmeos:meos:1.0.flink-processordepends on those coordinates and the facade generator reads that jar, in place of the committed, system-scopedflink-processor/jar/JMEOS.jar.The jar surface, the generated
MeosOps*facades, and thelibmeos.sothe smoke tests load all track master together, so the facades stay in lockstep with the surface they build against.tools/meos-source-commit.txtis dropped.regen_baseline.shcreates its output directory, since the baseline is a gitignored build artifact absent from a fresh checkout.Coverage
The facade generator emits
MeosOps*over the installed jar's surface ∩ the master-derived baseline; the smoke tests exercise them against the freshly built libmeos from/usr/local/lib.