Repository navigation
Test the raster aggregates the surface carries against MobilityDB - #88
Merged
estebanzimanyi merged 1 commit intoOct 25, 2026
Merged
Conversation
AggregatesCatalogTest registers rasterUnion, sameAlignmentAgg and summaryStatsAgg among the names of the catalog and tests their seven overloads over two rasters against MobilityDB's answers: the four forms of rasterUnion as the hex WKB of the united raster and sameAlignmentAgg as its boolean, among the overloads answering a text, and the two forms of summaryStatsAgg by the six fields of the summarystats record the aggregate answers, read in Java in the order of the record, since no SQL function of the surface reads a field of it. Witness: JMEOS's generator carries the aggregates answering a boolean or a structure and reading an integer or boolean argument, and MobilityDB reads the shorter raster aggregate forms as their siblings do, so the three names leave the list of names the surface leaves out. Measured: the two rows are tile 1 of the union tiles of MobilityDB's 500_raster and the same tile one tile east, sharing no pixel, so every pixel operation is independent of the order of the rows; the answers are those MobilityDB gives over them, harvested through its ctest harness: rasterUnion as ST_AsHexWKB writes it, and summaryStatsAgg (16, 80, 5, 2.7386127875258306, 1, 9) over band 1 and (18, 900, 50, 25.81988897471611, 10, 90) over band 2.
estebanzimanyi
added a commit
to estebanzimanyi/MobilityFlink
that referenced
this pull request
Oct 25, 2026
everyOverloadAnswersUnquoted calls each two-argument overload of the topological and position families as a query of its own, and each query is a job the mini-cluster plans and submits. The overloads now share their jobs: a hundred calls are the columns of one query, each column still required to answer a Boolean, and a query that fails is run again call by call through #scalar, so a failing overload is named by its own query and the innermost cause, as before. Measured: on the CI of main the step building and testing the binding takes 1274 s, against 154 s for MobilitySpark's, and TopologicalPositionSurfaceTest takes 1022 s of it for its three tests. A query costs 0.53 s on Flink and 0.08 s on Spark, read from AggregatesCatalogTest (288 queries in 152.7 s, 295 in 23.4 s), so the time is the jobs, not the calls. On the CI of this commit before its rebase onto MobilityDB#88 (fork run 40190727763), the three tests of TopologicalPositionSurfaceTest pass in 116.7 s.
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
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.
AggregatesCatalogTest registers rasterUnion, sameAlignmentAgg and summaryStatsAgg among the
names of the catalog and tests their seven overloads over two rasters against MobilityDB's
answers: the four forms of rasterUnion as the hex WKB of the united raster and sameAlignmentAgg
as its boolean, among the overloads answering a text, and the two forms of summaryStatsAgg by
the six fields of the summarystats record the aggregate answers, read in Java in the order of
the record, since no SQL function of the surface reads a field of it.
Witness: JMEOS's generator carries the aggregates answering a boolean or a structure and
reading an integer or boolean argument, and MobilityDB reads the shorter raster aggregate forms
as their siblings do, so the three names leave the list of names the surface leaves out.
Measured: the two rows are tile 1 of the union tiles of MobilityDB's 500_raster and the same
tile one tile east, sharing no pixel, so every pixel operation is independent of the order of
the rows; the answers are those MobilityDB gives over them, harvested through its ctest harness:
rasterUnion as ST_AsHexWKB writes it, and summaryStatsAgg (16, 80, 5, 2.7386127875258306, 1, 9)
over band 1 and (18, 900, 50, 25.81988897471611, 10, 90) over band 2.