Skip to content

runtime-next: remove hardcoded materialization ser_policy fallback#3140

Draft
dgreer-dev wants to merge 1 commit into
masterfrom
daveg/3139-ser-policy-defaults
Draft

runtime-next: remove hardcoded materialization ser_policy fallback#3140
dgreer-dev wants to merge 1 commit into
masterfrom
daveg/3139-ser-policy-defaults

Conversation

@dgreer-dev

Copy link
Copy Markdown
Contributor

Remove the last vestiges of the ser_policy defaults. All but three materializations already have the correct behavior, and a PR has been raised.

Marking this as a draft because we shouldn't merge until that PR has been deployed and all tasks using those connectors have been republished.

The runtime has sniffed endpoint config bytes for well-known connector
image names and applied a hardcoded truncation policy on match, because
those connectors couldn't yet negotiate one. Serialization policies are
now negotiated via the connector protocol: connectors return ser_policy
in their Validated response and it's baked into the built binding spec,
which build_binding already prefers.

All six formerly-hardcoded connectors now return ser_policy (redshift,
azure-fabric-warehouse, and sqlite as of estuary/connectors#4787), and
the 20-day periodic touch publication cycle refreshes every enabled
task's built spec, so the fallback is dead weight. Bindings without a
policy now get SerPolicy::noop().

This resolves the TODO(johnny) hack comment and the TODO(whb) removal
condition. The V1 runtime keeps its copy of the hack; it's deprecated
and not worth touching.
@dgreer-dev dgreer-dev requested a review from williamhbaker July 9, 2026 18:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant