This is an automated email from the ASF dual-hosted git repository.
fokko pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/iceberg.git
The following commit(s) were added to refs/heads/master by this push:
new b57e2c4016 Docs: Fix `expire_snapshots` broken link (#7943)
b57e2c4016 is described below
commit b57e2c40167d39c63477eae416c98e7d4ca2b8f2
Author: Rakesh Das <[email protected]>
AuthorDate: Thu Jun 29 22:21:56 2023 +0530
Docs: Fix `expire_snapshots` broken link (#7943)
---
docs/branching-and-tagging.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/branching-and-tagging.md b/docs/branching-and-tagging.md
index 575c366784..9a8e71f7f9 100644
--- a/docs/branching-and-tagging.md
+++ b/docs/branching-and-tagging.md
@@ -33,7 +33,7 @@ menu:
Iceberg table metadata maintains a snapshot log, which represents the changes
applied to a table.
Snapshots are fundamental in Iceberg as they are the basis for reader
isolation and time travel queries.
-For controlling metadata size and storage costs, Iceberg provides snapshot
lifecycle management procedures such as
[`expire_snapshots`](../../spark/spark-procedures/#expire-snapshots) for
removing unused snapshots and no longer neccessary data files based on table
snapshot retention properties.
+For controlling metadata size and storage costs, Iceberg provides snapshot
lifecycle management procedures such as
[`expire_snapshots`](../spark-procedures/#expire-snapshots) for removing unused
snapshots and no longer necessary data files based on table snapshot retention
properties.
**For more sophisticated snapshot lifecycle management, Iceberg supports
branches and tags which are named references to snapshots with their own
independent lifecycles. This lifecycle is controlled by branch and tag level
retention policies.**
Branches are independent lineages of snapshots and point to the head of the
lineage.
@@ -54,7 +54,7 @@ Tags can be used for retaining important historical snapshots
for auditing purpo
-The above diagram demonstrates retaininig important historical snapshot with
the following retention policy, defined
+The above diagram demonstrates retaining important historical snapshot with
the following retention policy, defined
via Spark SQL.
1. Retain 1 snapshot per week for 1 month. This can be achieved by tagging the
weekly snapshot and setting the tag retention to be a month.
