Sibling temporal families (cbuffer / npoint / pose / rgeo)#25
Open
estebanzimanyi wants to merge 3 commits into
Open
Sibling temporal families (cbuffer / npoint / pose / rgeo)#25estebanzimanyi wants to merge 3 commits into
estebanzimanyi wants to merge 3 commits into
Conversation
The MobilitySpark base UDF library — temporal, geo, boxes, time and set surfaces plus the base infrastructure — bound to the canonical single-source functions.GeneratedFunctions surface (the MEOS-API / meos-idl.json codegen output), bundled as libs/JMEOS-1.4.jar regenerated against the ecosystem pin, with lib/libmeos.so built from the pin (CBUFFER/NPOINT/POSE/RGEO + H3). Every UDF binds the generated surface directly; the legacy hand-rolled functions.functions facade is retired. The pg_-prefixed PG-compat I/O (pg_interval_in/out, pg_timestamptz_in) is preserved to disambiguate the PostgreSQL built-ins of the same name. CI builds libmeos from the ecosystem pin on Linux/macOS (with H3, and an in-source build dir so pgtypes/postgres.h's relative ../../meos/include resolves); Windows is non-blocking. Full unit suite green (907/907). The th3index, sibling (cbuffer/npoint/pose/rgeo) and portable-operator families stack on this foundation as separate changes; the BerlinMOD benchmark builds on the full surface.
The temporal H3-index (th3index) family for MobilitySpark, stacked on the foundation library: the h3index/th3index UDFs (Th3IndexUDFs), the H3 cell prefilter (Th3IndexPrefilterUDFs) and the JNR bindings, registered in the session. th3index is backed by libmeos built with -DH3=ON (the standalone library wires the h3 object library at the current ecosystem pin); the UDFs bind the generated functions.GeneratedFunctions surface (th3index_*, h3index_in/out, the canonicalized parse/to_string -> in/out). No change to the library surface, so the unit suite is unchanged (907/907).
The four sibling temporal families for MobilitySpark, stacked on the th3index change: CbufferUDFs, NpointUDFs, PoseUDFs and RgeoUDFs, each binding the generated functions.GeneratedFunctions surface for its family and registered in the session. No change to the foundation surface, so the unit suite is unchanged (907/907).
estebanzimanyi
force-pushed
the
feat/family-sibling
branch
from
89e2766 to
00c751d
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.
Stacked on #24 (th3index) → #22 (foundation). Adds the four sibling temporal families —
CbufferUDFs,NpointUDFs,PoseUDFs,RgeoUDFs— each binding the generatedfunctions.GeneratedFunctionssurface for its family and registered in the session.No foundation-surface change — unit suite unchanged (907/907). Review #22 then #24 first; this PR's own change is the sibling-families commit on top.