This is an automated email from the ASF dual-hosted git repository. lzljs3620320 pushed a commit to branch release-0.8 in repository https://gitbox.apache.org/repos/asf/paimon.git
commit 64e031343f7fdd80d2ac38b4d761ab7c149277c6 Author: Aiden <[email protected]> AuthorDate: Tue May 7 14:21:25 2024 +0800 [doc] add some descriptions about data writing in basic-concepts (#3301) --- docs/content/concepts/basic-concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/concepts/basic-concepts.md b/docs/content/concepts/basic-concepts.md index 0c57e2e34..3213ca429 100644 --- a/docs/content/concepts/basic-concepts.md +++ b/docs/content/concepts/basic-concepts.md @@ -67,7 +67,7 @@ By partitioning, users can efficiently operate on a slice of records in the tabl ## Consistency Guarantees Paimon writers use two-phase commit protocol to atomically commit a batch of records to the table. Each commit produces -at most two [snapshots]({{< ref "concepts/basic-concepts#snapshot" >}}) at commit time. +at most two [snapshots]({{< ref "concepts/basic-concepts#snapshot" >}}) at commit time. It depends on the incremental write and compaction strategy. If only incremental writes are performed without triggering a compaction operation, only an incremental snapshot will be created. If a compaction operation is triggered, an incremental snapshot and a compacted snapshot will be created. For any two writers modifying a table at the same time, as long as they do not modify the same partition, their commits can occur in parallel. If they modify the same partition, only snapshot isolation is guaranteed. That is, the final table
