Skip to content

Update extents-overview.md #2848

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

Merged
ttorble merged 1 commit into from
Feb 17, 2026
Merged

Update extents-overview.md #2848

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
3 changes: 3 additions & 0 deletions data-explorer/kusto/management/extents-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,9 @@ The common extent lifecycle is as follows:
1. The extent is merged with other extents.
1. The merged extent (possibly one that tracks its lineage to other extents) is eventually dropped because of a [retention policy](retention-policy.md).

> [!NOTE]
> The recommended maximum number of extents per cluster is 10,000,000

## Extent creation time

Two [datetime](../query/scalar-data-types/datetime.md) values are tracked per extent: `MinCreatedOn` and `MaxCreatedOn`. These values are initially the same but may change when the extent is merged with other extents. When the extent is merged with other extents, the new values are according to the original minimum and maximum values of the merged extents.
Expand Down