Skip to content

docs: correct the default materialization maxTxnDuration - #3347

Merged
jwhartley merged 1 commit into
masterfrom
docs/max-txn-duration-default
Aug 12, 2026
Merged

docs: correct the default materialization maxTxnDuration#3347
jwhartley merged 1 commit into
masterfrom
docs/max-txn-duration-default

Conversation

@jwhartley

Copy link
Copy Markdown
Contributor

Description:

Three places describe the default maxTxnDuration for materializations as five minutes. The actual default has been twenty minutes since d09cb56 (June 2025), which raised it deliberately. This corrects the text in all three; no behavior changes.

File Was Now
crates/models/src/shards.rs:35 five minutes twenty minutes
flow.schema.json:1284 five minutes twenty minutes
site/docs/features/configuring-task-shards.md:18 5 minutes 20 minutes

crates/assemble/src/lib.rs:411 is the authority and is unchanged:

} else if task_type == labels::TASK_TYPE_MATERIALIZATION {
    Duration::from_secs(20 * 60)

Workflow steps:

No change to how the field is used. A reader of the docs page or the JSON schema now sees the default the runtime actually applies.

Documentation links affected:

Notes for reviewers:

Two things worth a look.

  1. flow.schema.json is edited in place rather than regenerated. The released flowctl v0.6.12 predates the syncSchedule model, so flowctl raw json-schema with it drops 102 lines of valid schema. The string I edited is the verbatim serialization of the doc comment, so this is byte-identical to what an in-tree regeneration emits, and the CI check added in d4583de should confirm that.
  2. The docs page is not generated from the schema, despite carrying nearly the same text. Its wording diverges (an extra sentence about commit completion time, and reversed clause order), so it is a third independent copy that nothing keeps in sync. That is why this drifted for 14 months and it will drift again. Out of scope here, but worth someone deciding whether that table should be generated.

The default was raised from 5m to 20m in d09cb56 (June 2025), but three descriptions of it were left behind: the ShardTemplate doc comment, its generated entry in flow.schema.json, and the hand-written table in the Configuring Task Shards page.

No behavior change. The 20 minute default in assemble is intentional and unchanged; only the text describing it is corrected.

flow.schema.json is edited in place rather than regenerated, because the released flowctl predates syncSchedule and regenerating with it would drop valid schema. The edited string is byte-identical to what an in-tree regeneration emits.
@github-actions

Copy link
Copy Markdown

🚀 Preview deployed to https://docs.estuary.dev/pr-preview/pr-3347/

📄 Changed pages:

@jwhartley
jwhartley requested review from a team and aeluce August 12, 2026 00:57

@SeanWhelan SeanWhelan left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, LGTM

@jwhartley
jwhartley merged commit 6ba6ecf into master Aug 12, 2026
10 of 12 checks passed
@jwhartley
jwhartley deleted the docs/max-txn-duration-default branch August 12, 2026 21:27
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.

2 participants