Overview on Protobuf for Apache Flink DataStream

Quickstart

Mon, 01 Jan 0001 00:00:00 +0000

Run a native Protobuf DataStream job#

Run the standalone application example against a local build of the library, installed into an isolated Maven repository, or against the published library . Maven Central publishes 1.0.0 for Flink 2.x and 1.0.0-1.20 for Flink 1.20 LTS.

Build the development artifact#

Install mise , then clone this repository. mise install provides Python 3.14 and uv for the recipe’s standard-library checks. Run these commands from its root with JDK 17:

Usage and configuration

Mon, 01 Jan 0001 00:00:00 +0000

Configure native Protobuf values#

The quickstart builds and runs the application examples. The public application entrypoints are ProtobufTypeInformation and ProtobufTypeInfoFactory. The serializer and snapshot classes are internal machinery; construct types through the public factory or builder.

Explicit type information#

Use explicit type information for .returns(...) and per-type settings. The following construction example uses the generated full-runtime Event class from the quickstart. The explicit example shows the imports for these types.

ProtobufTypeInformation comes from this library; Event comes from the application’s generated code. Replace the Event import and class reference with the application’s message type. The example’s event.proto sets java_package = "io.github.flink.gcp.protobuf.examples.generated" and java_multiple_files = true, so Event is a top-level class in that Java package.

DynamicMessage values

Mon, 01 Jan 0001 00:00:00 +0000

DynamicMessage values#

com.google.protobuf.DynamicMessage holds a Protobuf message whose schema comes from a descriptor at runtime rather than from a generated class. The library transports these values and keeps them in managed state when the application supplies type information bound to a root descriptor.

The DynamicMessage example is compiled and run with the other quickstart examples; the snippets below come from it. ADR-0005 records the design.

DynamicMessage and generated common types#

Several generated message types also carry data whose shape varies at runtime. They are a different tool: their schema is fixed and known to the library through their generated class.

State compatibility

Mon, 01 Jan 0001 00:00:00 +0000

Protobuf updates and state compatibility#

Adding a field can preserve Protobuf binary compatibility, and the current development library restores state across that change. It accepts unchanged schemas and the supported schema changes , and it rejects other changes to the declarations that saved values reach when the job restores its state. Version 1.0.0 is the first release published to Maven Central; the 0.x versions were unpublished development milestones.

Development builds before 1.0.0#

A build of this source is the development version 1.0.0-SNAPSHOT, which restores supported schema changes. The 0.x versions are development milestones, not releases, and their APIs, defaults, runtime requirements, and state formats are not compatibility contracts. Retain the exact source revision and artifact checksums alongside schemas and state; a SNAPSHOT version alone does not identify their writer.

Supported types

Mon, 01 Jan 0001 00:00:00 +0000

Google Well-Known Types and OpenTelemetry values#

Google Well-Known Types (WKT) and OpenTelemetry composite values use generated message classes with declared descriptors. They use the same ProtobufTypeInformation and serializer as application messages. Changing a Struct key or choosing another AnyValue variant changes the data within that descriptor, so unchanged-schema restoration supports those changes.

Tested types#

Types	Tested values
Google `Struct`, `Value`, `ListValue`	Nested maps and lists, null, booleans, strings, numbers, empty containers, and unset versus present-default oneof cases
Google `Any`	Default values, a type URL and opaque bytes, and nesting inside an application message
Google `Timestamp`, `Duration`, `Empty`, `FieldMask`	Defaults, representative populated messages, and nested use
Google `DoubleValue`, `FloatValue`, `Int64Value`, `UInt64Value`, `Int32Value`, `UInt32Value`, `BoolValue`, `StringValue`, `BytesValue`	Default and populated wrappers, including a present wrapper containing a default scalar
OTel `AnyValue`, `ArrayValue`, `KeyValueList`, `KeyValue`	Nested heterogeneous values, bytes, empty containers, unset and all eight present oneof cases, and profiling string/key dictionary indices

Wrappers remain supported for existing schemas. For new schemas, prefer explicit field presence, such as proto3 optional, as described in the WKT guidance .

Development

Mon, 01 Jan 0001 00:00:00 +0000

Development#

Toolchain#

The Maven Wrapper pins Maven 3.10.0; all Maven recipes in just invoke the wrapper. The default local JDK is Temurin 17, and CI runs Temurin 17 and 21. Java output targets release 17. mise.toml supplies just, the workflow and Markdown linters, pinact, Python 3.14, uv, Hugo Extended 0.164.0, and Go 1.26.5. Maven supplies Java build plugins and protoc; protoc does not need to be on PATH. The repository’s Python tools and their tests use the non-packaged uv project at the root. mise.toml provides Python 3.14, requires-python = "==3.14.*" in pyproject.toml limits uv to that minor, and uv.lock locks pytest and PyYAML as development dependencies. pyproject.toml sets python-preference = "only-system" and python-downloads = "never", so uv takes Python 3.14 from PATH, where mise x and mise activation put the mise.toml interpreter, and fails rather than download one. An activated virtual environment or an existing .venv takes precedence over PATH; deactivate other environments and delete a .venv built from another interpreter. Manage Python with mise, including the global default, rather than uv python install or uv python pin --global; the repository has no .python-version, so a global uv pin can override the mise interpreter or make the recipes fail. Recipes run the tools with uv run --locked --isolated --no-dev: each run uses a temporary environment with only the standard library, and a stale lock fails instead of being rewritten. These recipes take uv from PATH, which mise x -- just or a mise-activated shell provides.

Documentation versions

Mon, 01 Jan 0001 00:00:00 +0000

Documentation versions#

Before 1.0.0, the site contains Development from main and each 0.x development milestone. A milestone is a published GitHub pre-release tagged v0.Y.Z; the site keeps the latest patch of each 0.x minor and labels it, for example, 0.1 (development milestone). A milestone page shows only its tagged source, so behavior added on main afterwards appears only in Development. Neither Development nor milestone documentation implies that artifacts are available on Maven Central. Existing development evidence remains in the source tree. Milestones leave the site when the first stable release is published.

Mon, 01 Jan 0001 00:00:00 +0000

ADR-0006: Releases stage both artifact lines on the Central Portal and publish after both validate#

Status: Accepted
Date: 2026-10-31
Issue: #13
Implements: The publication requirements of ADR-0003
Implementation: The release build, bundle inspection, unsigned CI rehearsal, Release workflow, and Central Portal helper are implemented; version 1.0.0 is the first publication through them
Current instructions: Release artifacts and Publishing a release

Context#

Version 1.0.0 is the first Maven Central publication of io.github.flink-gcp:flink-datastream-protobuf. Central never deletes or replaces a published version, so a defect found after publication requires a new version. ADR-0003 requires two artifact lines from one source revision, X.Y.Z built at the Flink 2.x floor and X.Y.Z-1.20 built for Flink 1.20, a guard on Maven’s effective model before publication, and validation of both before either is published.

ADR-0001: Native Protobuf type integration for DataStream

Mon, 01 Jan 0001 00:00:00 +0000

ADR-0001: Native Protobuf type integration for DataStream#

Status: Accepted
Date: 2026-09-06
Publication policy amended: 2026-09-13; 0.x versions are unpublished development milestones and 1.0.0 is the first Maven Central release
Release contract amended: 2026-09-08, issue #7
Frame buffering amended: 2026-10-11, issue #42
Sizing traversal amended: 2026-10-19, issue #43
Generated sizes for bounded types amended: 2026-10-22, issue #112
Large-frame reads amended: 2026-10-25, issue #113
DynamicMessage design: 2026-10-29, extended by ADR-0005
1.0.0 persisted-format restart amended: 2026-10-29, issue #140
Protobuf 4 build baseline amended: 2026-10-30, issue #141
Implementation: Serializer, type integration, and descriptor snapshots implemented; the 0.2.0 descriptor evaluator is implemented, tested with descriptor pairs, and used by snapshot restore; MiniCluster tests verify runtime recovery with unchanged schemas and supported schema changes from state written by the same development build (issue #16 ); the 1.0.0 format restart is implemented, and the library does not read state written by 0.x milestones (issue #140 )
Evidence: Spike 0
Runtime scope superseded: 2026-09-10, ADR-0003

Context#

Flink uses TypeInformation to select serializers for operator transport and managed state. Generated Protobuf messages otherwise fall back to generic serialization in the tested configuration. The goal is an explicit native integration that works with pipeline.generic-types: false and owns a documented checkpoint/savepoint compatibility policy. Connector boundary SerializationSchema and DeserializationSchema implementations, and Table/SQL formats, are separate concerns.

ADR-0002: A single Maven module with a shared local and CI workflow

Mon, 01 Jan 0001 00:00:00 +0000

ADR-0002: A single Maven module with a shared local and CI workflow#

Status: Accepted
Date: 2026-09-06
Release contract amended: 2026-09-08, issue #7
Dependency update policy amended: 2026-09-12
Benchmark Avro and Jackson update exclusions amended: 2026-10-11
Benchmark Avro and Jackson convergence check amended: 2026-10-12, issue #84
Maven dependency graph submission amended: 2026-10-12, issue #82
Development bundle tooling amended: 2026-09-16, issue #40
CI compiler reuse and job budgets amended: 2026-10-11, issue #46 ; evidence: CI budget measurements
Retained baseline retrieval amended: 2026-10-11, issue #61
Python tooling through uv amended: 2026-10-12, issue #96
Development milestone documentation amended: 2026-10-19, issue #62
Required CI passed ruleset amended: 2026-10-19
CI Maven mirror and shared repository cache amended: 2026-10-30, issue #135
Retained 0.x checks ended by the 1.0.0 format restart: 2026-10-31, issue #140
Current instructions: Development and Contributing

Decision#

Use one jar module with Maven coordinates io.github.flink-gcp:flink-datastream-protobuf, starting at 0.1.0-SNAPSHOT. Develop it in the flink-gcp organization without depending on flink-connector-gcp. Reuse that project’s Apache-2.0 licensing, collective copyright identity, Maven Wrapper, connector parent 2.0.0, mise/just entry points, Java formatting, Checkstyle, Apache RAT, JUnit 5, and AssertJ conventions. The project metadata and packaged notices identify The flink-gcp authors rather than inheriting ASF ownership. Keep third-party attribution on the Apache-derived Checkstyle files.

ADR-0003: Support current/previous Flink 2.x minors and Flink 1.20 LTS

Mon, 01 Jan 0001 00:00:00 +0000

ADR-0003: Support current/previous Flink 2.x minors and Flink 1.20 LTS#

Status: Accepted
Date: 2026-09-10
Supersedes: The Flink 2.3-only runtime scope in ADR-0001
Amends: The build matrix in ADR-0002
Unchanged-jar check amended: 2026-10-30, issue #141
Release discovery amended: 2026-10-31, issue #142
Current instructions: Development

Context#

The maintainer wants Flink 1.20 and 2.x support under the same policy as flink-connector-gcp. Compiling separately on each runtime establishes source compatibility but cannot prove that a released jar works on both supported 2.x minors. The 1.20 TypeInformation API still requires createSerializer(ExecutionConfig), while Flink 2.x removed it. The existing test factory therefore needs a small adapter, even though the production serializer currently compiles unchanged. Flink 1.20 also does not infer native list element information from the probe’s TypeHint.

ADR-0004: Opt-in serializer benchmarks with explicit comparison contracts

Mon, 01 Jan 0001 00:00:00 +0000

ADR-0004: Opt-in serializer benchmarks with explicit comparison contracts#

Status: Accepted
Date: 2026-09-12
Evidence content gate added: 2026-09-18, issue #41
Temporary GCE execution added: 2026-10-11, issue #44
Paired native/Chill mode added: 2026-10-11, issue #42
Variant placement calibrated: 2026-10-21, issue #109
Pairwise comparison placement added: 2026-10-22, issue #115
DynamicMessage lanes added: 2026-10-31, issue #45
Issue: #30

Decision#

Keep the single production Maven module and add a benchmarks profile with test-scoped JMH, Avro, Thrift, Chill, and Jackson result-reader dependencies. Compile handwritten benchmark sources and generated records into test outputs only. Keep the compiler toolchain optional and generated Java under target. Do not publish a benchmark classifier, add production dependencies, or change the native serializer API for measurement.

ADR-0005: Descriptor-bound DynamicMessage type and snapshot contracts

Mon, 01 Jan 0001 00:00:00 +0000

ADR-0005: Descriptor-bound DynamicMessage type and snapshot contracts#

Status: Accepted
Date: 2026-10-29
Issue: #21
Extends: The generated-message contracts in ADR-0001 , which apply here except where this record states otherwise
Implementation: Implemented by issue #22 ; issue #23 validated state recovery and the upgrade paths and documented usage
1.0.0 persisted-format restart: 2026-10-31, issue #140 renamed the dynamic snapshot class and kept its layout

Context#

The 0.1.0 and 0.2.0 development milestones support generated full-runtime messages only. Type information, serializers, and snapshots identify a payload type by its generated class, and the class supplies the descriptor, parser, and default instance. The 0.3.0 milestone adds com.google.protobuf.DynamicMessage, which an application creates from a descriptor without a generated class.

Aliased large-frame reads in the native serializer

Mon, 01 Jan 0001 00:00:00 +0000

Aliased large-frame reads in the native serializer#

This report measures the large-frame read path changed for #113 . After the generated-size change , large deserialize and deserializeReuse were the only cells that missed the ADR-0004 native/Chill tolerance on both profiles, at 1.26 to 1.27 times Chill’s time with about 132 KB/op allocated for a 64 KiB payload. One plan on temporary GCE VMs compares the change with the unchanged serializer. The measurement contract is ADR-0004 ; the comparison does not establish whole-job throughput, heap retention, or state compatibility.

Architecture decisions

Mon, 01 Jan 0001 00:00:00 +0000

Architecture decisions#

Record	Decision	Status
ADR-0001	Native Protobuf type integration for DataStream	Accepted
ADR-0002	A single Maven module with a shared local and CI workflow	Accepted
ADR-0003	Current/previous Flink 2.x minors and a separate 1.20 LTS build	Accepted; replaces ADR-0001’s runtime scope
ADR-0004	Opt-in serializer benchmarks and practical comparison contract	Accepted
ADR-0005	Descriptor-bound DynamicMessage type and snapshot contracts	Accepted; extends ADR-0001; implemented and validated
ADR-0006	Both artifact lines are staged on the Central Portal and published after both validate	Accepted; implemented

These records distinguish accepted design from implemented behavior. The native serializer, application-facing type integration, and versioned descriptor snapshots are implemented. MiniCluster tests verify checkpoint recovery and savepoint restoration with HashMap and RocksDB state backends, including supported schema changes. A refinement updates its existing record; a reversal adds a new record and marks the old one as superseded.

CI compiler reuse and job budgets

Mon, 01 Jan 0001 00:00:00 +0000

CI compiler reuse and job budgets#

This page records the GitHub runner durations behind the Verify job limits and the benchmark compiler cache from #46 . The development guide describes the current procedure, and ADR-0002 records the decision and the rejected alternatives. These are budget measurements on shared runners, not benchmark results; no CI check compares them with a threshold.

Method#

Durations come from the started_at and completed_at timestamps of jobs and steps in the GitHub Actions jobs API. Only successful jobs are counted, including successful jobs in runs where another job failed or the run was cancelled; every step value is that step’s own duration. All jobs ran on ubuntu-latest standard runners; the measured runs after the change reported Ubuntu 24.04 on x86_64 in the compiler cache key. Medians of an even number of jobs are the mean of the two middle values. GitHub announced that ubuntu-latest moves to Ubuntu 26 from 2026-10-19; that changes the distribution release in the key, and these durations do not describe the new image. A matrix job is one of the ten runtime/JDK/Protobuf builds; the binary compatibility and development bundle jobs are reported as whole jobs.

Coded-stream buffer allocation in the native serializer

Mon, 01 Jan 0001 00:00:00 +0000

Coded-stream buffer allocation in the native serializer#

This report measures the per-record coded-stream buffers investigated in #42 . It separates the output and input buffers with controlled variants of one source tree and compares each with the unchanged serializer on the same VM. The measurement contract is ADR-0004 ; the comparison does not establish whole-job throughput or state compatibility.

Change under test#

Before the change, every serialize call wrapped the target view in CodedOutputStream.newInstance(OutputStream), and every deserialize call wrapped a bounded frame stream in CodedInputStream.newInstance(InputStream). In the pinned Protobuf 3.25.9 and 4.33.6 runtimes, both factories allocate a 4,096-byte buffer for each call.

Development artifact bundles

Mon, 01 Jan 0001 00:00:00 +0000

Development artifact bundles#

Issue #40 prepared fixed development inputs for the state and API checks in #16 and #17. The final v0.1.0, v0.2.0, and v0.3.0 bundles are retained as assets of the v0.1.0 pre-release , the v0.2.0 pre-release , and the v0.3.0 pre-release . The tooling labels a development capture development-tooling-baseline with milestone.final=false; a successful capture alone does not designate a milestone baseline. No 0.x coordinates are published to Maven Central. The 1.0.0 format restart (#140 ) removed the 0.x snapshot classes, so the current library does not restore the state in these bundles; they remain retained development records. The capture, check, read, restore, API, and consumer commands also apply to bundles that published releases write, starting with 1.0.0; retain a published release describes their capture and retention.

Generated sizes for small writes in the native serializer

Mon, 01 Jan 0001 00:00:00 +0000

Generated sizes for small writes in the native serializer#

This report measures the generated-size path added for #112 . After the sizing-traversal change , scalar and nested serialize and serializeSameInstance still took 2.4 to 2.9 times Chill’s time, collections writes 2.0 to 2.5 times, and scalar and nested buildAndSerialize 1.5 to 1.6 times, while a diagnostic variant without safe sizing met the ADR-0004 tolerance in almost every cell. One plan on temporary GCE VMs compares the change with the unchanged serializer. The measurement contract is ADR-0004 ; the comparison does not establish whole-job throughput or state compatibility.

Runtime state recovery

Mon, 01 Jan 0001 00:00:00 +0000

Runtime state recovery#

For resource locations, build/test invocation, capture, and dependency updates, see Test resources and version updates . This page records the recovery scenarios and their measured scope.

ProtobufRecoveryITCase executes the production serializer in a two-TaskManager MiniCluster with parallelism 2 and max parallelism 16. It uses stable integer stream keys, string MapState user keys, and generated messages as values in ValueState, MapState, and operator ListState. HashMap and RocksDB backends run the same cases. The ValueState implementation is checked at runtime to distinguish the selected backends.

Serializer benchmarks for the 0.1.0 development milestone

Mon, 01 Jan 0001 00:00:00 +0000

Serializer benchmarks for the 0.1.0 development milestone#

This report compares equivalent logical records through Flink serializers. The benchmark is development tooling and makes no production API or state-compatibility promise. The measurement contract is ADR-0004 .

Reproduce#

The ordinary build does not require benchmark tools. Run these commands from the v0.1.0 tag, whose benchmark pins differ from later revisions, with a compiler cache directory that has not built another Thrift version. For opt-in generation, install CMake, Flex, Bison 3.8 or newer, and a C++ compiler; build the pinned Thrift 0.23.0 compiler in an external cache:

Serializer benchmarks for the 1.0.0 release candidate

Mon, 01 Jan 0001 00:00:00 +0000

Serializer benchmarks for the 1.0.0 release candidate#

This report is the release-candidate performance evidence for 1.0.0 that #45 requires. It repeats the long serializer benchmarks of the 0.1.0 report on temporary Google Compute Engine VMs, with the same corpus, lanes, operations, fork and iteration settings, paired blocks, and practical tolerance, all defined in ADR-0004 . It adds the two DynamicMessage lanes that ADR-0004 describes. The results describe the recorded VMs and runtimes; they do not rank serializers universally and do not establish whole-job throughput or saved-state compatibility.

Serializer implementation performance check

Mon, 01 Jan 0001 00:00:00 +0000

Serializer implementation performance check#

This local comparison measures the getter-name removal, metadata cache, and sizing refactor against commit f6a6e33d272f74da80f82e9d77718399cda9702e. The candidate is the implementation accompanying this report. It is a small implementation comparison, not a ranking against other formats or an end-to-end Flink throughput result. The maintained cross-format harness and its v0.1.0 baseline work are described in the serializer benchmark report , tracked in #30 .

Conditions#

Measurements ran on 2026-09-11 using an Apple M1 Pro with 32 GiB RAM, macOS 26.6.2, and Temurin 17.0.20+8. Both variants used Flink 2.3.0, JMH 1.37, G1 GC, a fixed 256 MiB heap, and one benchmark thread. Protobuf runtime and generated fixtures were paired at 3.25.8 and 4.33.6 in separate classpaths. Each case used two JVM forks, three 500 ms warmup iterations, five 500 ms measurement iterations, average time mode, and the JMH GC profiler. Final comparisons ran sequentially without concurrent builds or another benchmark. The table reports the JMH mean and its 99.9% confidence interval half-width; allocated bytes are rounded per operation. These short runs on a development machine cannot establish small performance differences reliably.

Site licenses

Mon, 01 Jan 0001 00:00:00 +0000

Site licenses#

The shared design and version controls are licensed under Apache-2.0 by The flink-gcp authors. The Apache-2.0 license also covers this library. Fuse.js v7.3.0 is Copyright (c) 2026 Kiro Risk and is distributed under Apache-2.0; its notice is retained in the bundled search module. The following notices accompany the theme and its bundled normalization stylesheet.

Hugo Book v0.14.0#

The MIT License (MIT)

Copyright (c) 2018 Alex Shpak

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

modern-normalize v3.0.1#

MIT License

Copyright (c) Sindre Sorhus <sindresorhus@gmail.com> (https://sindresorhus.com)
Copyright (c) Jonathan Neal
Copyright (c) Nicolas Gallagher

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Sizing traversal allocation in the native serializer

Mon, 01 Jan 0001 00:00:00 +0000

Sizing traversal allocation in the native serializer#

This report measures the safe-sizing traversal investigated in #43 . After the buffer-allocation change , scalar and nested serialize and serializeSameInstance still took 6.2 to 7.0 times Chill’s time and allocated 1.9 to 2.2 KB/op; the 0.1.0 diagnostics had sampled allocation sites in the safe-sizing traversal. Two plans measure the change on temporary GCE VMs: one compares the final change with the unchanged serializer, and an earlier one separates the traversal bookkeeping, the descriptor work, and the remaining sizing cost from the output work with controlled variants. The measurement contract is ADR-0004 ; the comparison does not establish whole-job throughput or state compatibility.

Spike 0 validation

Mon, 01 Jan 0001 00:00:00 +0000

Spike 0 validation#

Outcome#

On 2026-09-06, the required superclass-registration and three transport paths passed on Flink 2.3.0 with both tested Protobuf runtimes and both JDKs. The stop condition did not occur, so the project can proceed with configuration registration as a supported design path alongside explicit TypeInformation.

The initial Chill transport succeeded: Chill 0.7.6 transported a StringValue while Kryo 5.6.2 was loaded. H1 is not supported by this observation. The experiment did find both Kryo major versions in the dependency graph; their coexistence did not make this particular job fail.

Variant placement across temporary GCE VMs

Mon, 01 Jan 0001 00:00:00 +0000

Variant placement across temporary GCE VMs#

This report calibrates the comparison of benchmark variants that run on different VMs of one plan, for #109 . The temporary GCE procedure measured every variant of a profile sequentially on one VM, so a plan’s wall-clock time grows with its variant count: each just benchmark-pair variant takes about 70 minutes. Placing each variant on its own VM would make that time independent of the variant count, but it compares variants across hosts. The ADR-0004 native/Chill protocol controls host speed within each block, and this calibration measures how much of the between-VM difference that control leaves.