-
Notifications
You must be signed in to change notification settings - Fork 3.5k
Expand file tree
/
Copy pathAppendFiles.java
More file actions
60 lines (58 loc) · 2.64 KB
/
Copy pathAppendFiles.java
File metadata and controls
60 lines (58 loc) · 2.64 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
*/
package org.apache.iceberg;
/**
* API for appending new files in a table.
*
* <p>This API accumulates file additions, produces a new {@link Snapshot} of the table, and commits
* that snapshot as the current.
*
* <p>When committing, these changes will be applied to the latest table snapshot. Commit conflicts
* will be resolved by applying the changes to the new latest snapshot and reattempting the commit.
*/
public interface AppendFiles extends SnapshotUpdate<AppendFiles> {
/**
* Append a {@link DataFile} to the table.
*
* @param file a data file
* @return this for method chaining
*/
AppendFiles appendFile(DataFile file);
/**
* Append a {@link ManifestFile} to the table.
*
* <p>The manifest must contain only appended files. All files in the manifest will be appended to
* the table in the snapshot created by this update.
*
* <p>The manifest will be used directly if snapshot ID inheritance is enabled (all tables with
* the format version > 1 or if the inheritance is enabled explicitly via table properties).
* Otherwise, the manifest will be rewritten to assign all entries this update's snapshot ID.
*
* <p>If the manifest is rewritten, it is always the responsibility of the caller to manage the
* 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
*/
AppendFiles appendManifest(ManifestFile file);
}