Carry a value of any size through the Flink serializer - #66
Merged
estebanzimanyi merged 1 commit intoSep 28, 2026
Merged
Conversation
A MEOS value crosses Flink as the WKB bytes of its type where the catalog states that byte codec, and the serializer writes the length of the form and its bytes. GeneratedSqlSurfaceTest builds its hex literals from a value's toString, the hex of its WKB, and aValueOfAnySizeCrossesTheSerializer serializes a 20,000-instant tgeompoint and reads it back to the same value with its 20,000 instants. GENERATION.md states the codec order: WKB bytes, then hex WKB, then text. Witness. The new test fails on the generator of JMEOS main with UTFDataFormatException: Encoded string is too long: 1160018, the hex form of that trajectory. Measured. Against JMEOS #111, the catalog and libmeos of MobilityDB 438528db44 with MEOS-API 20efba81be and the jar JMEOS builds from them, the binding runs 17 tests and the benchmark 12, all passing. Why. A trajectory of an ordinary day passes the 65,535 bytes a string write carries, and a value that cannot be serialized cannot be shuffled or checkpointed.
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.
A MEOS value crosses Flink as the WKB bytes of its type where the catalog states that byte
codec, and the serializer writes the length of the form and its bytes. GeneratedSqlSurfaceTest
builds its hex literals from a value's toString, the hex of its WKB, and
aValueOfAnySizeCrossesTheSerializer serializes a 20,000-instant tgeompoint and reads it back
to the same value with its 20,000 instants. GENERATION.md states the codec order: WKB bytes,
then hex WKB, then text.
Witness. The new test fails on the generator of JMEOS main with UTFDataFormatException:
Encoded string is too long: 1160018, the hex form of that trajectory.
Measured. Against JMEOS #111, the catalog and libmeos of MobilityDB 438528db44 with MEOS-API
20efba81be and the jar JMEOS builds from them, the binding runs 17 tests and the benchmark 12,
all passing.
Why. A trajectory of an ordinary day passes the 65,535 bytes a string write carries, and a
value that cannot be serialized cannot be shuffled or checkpointed.