[iceberg-docs] branch asf-site updated: deploy: 9997c3513e2760172c6307c4cd0e6277a432836c

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/iceberg-docs.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new fd68da3  deploy: 9997c3513e2760172c6307c4cd0e6277a432836c
fd68da3 is described below

commit fd68da3e150260f20bb0d0fbd852b6d895159836
Author: jackye1995 <ja...@users.noreply.github.com>
AuthorDate: Tue Feb 8 04:27:03 2022 +0000

    deploy: 9997c3513e2760172c6307c4cd0e6277a432836c
---
 img/iceberg-metadata.png | Bin 0 -> 140290 bytes
 spec/index.html          |   2 +-
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/img/iceberg-metadata.png b/img/iceberg-metadata.png
new file mode 100644
index 0000000..48a1b0c
Binary files /dev/null and b/img/iceberg-metadata.png differ
diff --git a/spec/index.html b/spec/index.html
index ef357da..bea7dc4 100644
--- a/spec/index.html
+++ b/spec/index.html
@@ -94,7 +94,7 @@
 <li><strong>Formats</strong> &ndash; Underlying data file formats will support identical schema evolution rules and types. Both read- and write-optimized formats will be available.</li>
 </ul>
 <h2 id=overview>Overview</h2>
-<p><img src=../img/iceberg-metadata.png alt="Iceberg snapshot structure">{.spec-img}</p>
+<p><img src=../../../img/iceberg-metadata.png alt="Iceberg snapshot structure"></p>
 <p>This table format tracks individual data files in a table instead of directories. This allows writers to create data files in-place and only adds files to the table in an explicit commit.</p>
 <p>Table state is maintained in metadata files. All changes to table state create a new metadata file and replace the old metadata with an atomic swap. The table metadata file tracks the table schema, partitioning config, custom properties, and snapshots of the table contents. A snapshot represents the state of a table at some time and is used to access the complete set of data files in the table.</p>
 <p>Data files in snapshots are tracked by one or more manifest files that contain a row for each data file in the table, the file&rsquo;s partition data, and its metrics. The data in a snapshot is the union of all files in its manifests. Manifest files are reused across snapshots to avoid rewriting metadata that is slow-changing. Manifests can track data files with any subset of a table and are not associated with partitions.</p>