From 7f6a798b1a7523e66a1249757855b3fc8812f955 Mon Sep 17 00:00:00 2001 From: aokolnychyi Date: Tue, 12 Dec 2023 23:23:58 +0100 Subject: [PATCH] Update doc --- api/src/main/java/org/apache/iceberg/AppendFiles.java | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/api/src/main/java/org/apache/iceberg/AppendFiles.java b/api/src/main/java/org/apache/iceberg/AppendFiles.java index e36df7af20c9..276ec9ae7c22 100644 --- a/api/src/main/java/org/apache/iceberg/AppendFiles.java +++ b/api/src/main/java/org/apache/iceberg/AppendFiles.java @@ -47,12 +47,11 @@ public interface AppendFiles extends SnapshotUpdate { * Otherwise, the manifest will be rewritten to assign all entries this update's snapshot ID. * *

If the manifest is rewritten, it is always the responsibility of the caller to manage the - * lifecycle of the original manifest. If manifest entries are allowed to inherit the snapshot ID - * assigned on commit, the manifest should never be deleted manually if the commit succeeds as it - * will become part of the table metadata and will be cleaned upon expiry. If the manifest gets - * merged with others while preparing a new snapshot, it will be deleted automatically if this - * operation is successful. If the commit fails, the manifest will never be deleted, and it is up - * to the caller whether to delete or reuse it. + * lifecycle of the original manifest. If the manifest is used directly, it should never be + * deleted manually if the commit succeeds as it will become part of the table metadata and will + * be cleaned upon expiry. If the manifest gets merged with others while preparing a new snapshot, + * it will be deleted automatically if this operation is successful. If the commit fails, the + * manifest will never be deleted, and it is up to the caller whether to delete or reuse it. * * @param file a manifest file * @return this for method chaining