Skip to content

[docs] Improve historical partition restart warning - #4441

Open
luoyuxia wants to merge 1 commit into
apache:mainfrom
luoyuxia:docs/historical-partition-warning-main
Open

luoyuxia wants to merge 1 commit into
apache:mainfrom
luoyuxia:docs/historical-partition-warning-main

Conversation

@luoyuxia

Copy link
Copy Markdown
Contributor

Generated-by: Codex (GPT-5) following the guidelines

Purpose

Linked issue: N/A (documentation follow-up to #4421)

The historical partition restart warning currently appears before the feature explanation and its
configuration example. Place the warning next to the action that requires the restart so readers
see the operational requirement at the relevant point in the workflow.

Brief change log

  • Move the writer and lookup job restart warning after the ALTER TABLE example.
  • Clarify that existing jobs must restart after either enabling or disabling the option.
  • Rely on the warning admonition for emphasis instead of bolding its full contents.

Tests

  • git diff --check
  • ./mvnw spotless:check
  • cd website && npm run build (the build reached link validation and then failed on existing
    site-wide /blog/ broken links unrelated to this change)

API and Format

No API or storage format changes.

Documentation

Improves the placement and wording of the historical partition restart warning.

Place the restart requirement next to the configuration example and clarify that it applies when the option is enabled or disabled.

Co-Authored-By: Codex <noreply@openai.com>
AI-Model: gpt-5

(cherry picked from commit 8b61e8b)

AI-Contributed/Feature: 12/12
AI-Contributed/UT: 0/0
@luoyuxia
luoyuxia force-pushed the docs/historical-partition-warning-main branch from 5990dd2 to e4110ad Compare September 21, 2026 08:04
@luoyuxia
luoyuxia marked this pull request as ready for review September 21, 2026 08:06
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