Skip to content

[docs] Improve historical partition restart warning #4441

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
luoyuxia wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[docs] Improve historical partition restart warning #4441

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions website/docs/table-design/data-distribution/partitioning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,12 +73,6 @@ In this case, when automatic partitioning occurs (Fluss will periodically operat

Before using historical partition access, make sure the [Paimon server-side setup](../../streaming-lakehouse/datalake-formats/paimon.md#historical-partition-access-setup) is completed.

:::warning
**After changing `table.datalake.historical-partition.enabled`, restart existing writer and lookup
jobs that need historical partition access so that their clients load the updated table
configuration.**
:::

Auto partitioning eventually removes partitions that fall outside the configured retention window.
After an original Fluss partition is removed, late records cannot be written to it and primary-key
lookups cannot find its rows in Fluss, even when the existing data has already been tiered to
Expand All @@ -94,6 +88,12 @@ ALTER TABLE my_partitioned_table SET (
);
```

:::warning
After enabling or disabling `table.datalake.historical-partition.enabled`, restart any existing
writer and lookup jobs that require historical partition access so that their clients reload the
updated table configuration.
:::

When enabled, the Coordinator creates and retains an internal `__historical__` system partition:

- **Writes:** Log tables and primary-key tables route records for expired partitions through the
Expand Down
Loading