This is an automated email from the ASF dual-hosted git repository.
blue pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/iceberg.git
The following commit(s) were added to refs/heads/asf-site by this push:
new a15c3b4 Deployed ce9b02d18 with MkDocs version: 1.0.4
a15c3b4 is described below
commit a15c3b4aeba683171a067a68fce9b726500ba0ad
Author: Ryan Blue <[email protected]>
AuthorDate: Mon Jul 27 08:18:02 2020 -0800
Deployed ce9b02d18 with MkDocs version: 1.0.4
---
api/index.html | 15 ++++++++++++++-
configuration/index.html | 5 +++++
index.html | 2 +-
javadoc/0.9.0/search.js | 4 ++++
reliability/index.html | 2 +-
sitemap.xml | 44 ++++++++++++++++++++++----------------------
sitemap.xml.gz | Bin 228 -> 227 bytes
spark/index.html | 4 ++++
8 files changed, 51 insertions(+), 25 deletions(-)
diff --git a/api/index.html b/api/index.html
index 72f9bd2..96c1834 100644
--- a/api/index.html
+++ b/api/index.html
@@ -440,6 +440,18 @@ Iterable<CombinedScanTask> tasks = scan.planTasks();
<li><code>rollback</code> – roll the table state back by pointing
current to a specific snapshot</li>
</ul>
<h3 id="transactions">Transactions<a class="headerlink" href="#transactions"
title="Permanent link">¶</a></h3>
+<p>Transactions are used to commit multiple table changes in a single atomic
operation. A transaction is used to create individual operations using factory
methods, like <code>newAppend</code>, just like working with a
<code>Table</code>. Operations created by a transaction are committed as a
group when <code>commitTransaction</code> is called.</p>
+<p>For example, deleting and appending a file in the same transaction:</p>
+<pre><code class="java">Transaction t = table.newTrasaction();
+
+// commit operations to the transaction
+t.newDelete().deleteFromRowFilter(filter).commit();
+t.newAppend().appendFile(data).commit();
+
+// commit all the changes to the table
+t.commitTransaction();
+</code></pre>
+
<h2 id="types">Types<a class="headerlink" href="#types" title="Permanent
link">¶</a></h2>
<p>Iceberg data types are located in the <a
href="/javadoc/master/index.html?org/apache/iceberg/types/package-summary.html"><code>org.apache.iceberg.types</code>
package</a>.</p>
<h3 id="primitives">Primitives<a class="headerlink" href="#primitives"
title="Permanent link">¶</a></h3>
@@ -520,7 +532,8 @@ ListType list = ListType.ofRequired(1, IntegerType.get());
</ul>
<p>This project Iceberg also has modules for adding Iceberg support to
processing engines:</p>
<ul>
-<li><code>iceberg-spark</code> is an implementation of Spark’s
Datasource V2 API for Iceberg (use iceberg-runtime for a shaded version)</li>
+<li><code>iceberg-spark2</code> is an implementation of Spark’s
Datasource V2 API in 2.4 for Iceberg (use iceberg-spark-runtime for a shaded
version)</li>
+<li><code>iceberg-spark3</code> is an implementation of Spark’s
Datasource V2 API in 3.0 for Iceberg (use iceberg-spark3-runtime for a shaded
version)</li>
<li><code>iceberg-data</code> is a client library used to read Iceberg tables
from JVM applications</li>
<li><code>iceberg-pig</code> is an implementation of Pig’s LoadFunc API
for Iceberg</li>
<li><code>iceberg-runtime</code> generates a shaded runtime jar for Spark to
integrate with iceberg tables</li>
diff --git a/configuration/index.html b/configuration/index.html
index 374d821..c8df522 100644
--- a/configuration/index.html
+++ b/configuration/index.html
@@ -695,6 +695,11 @@ df.write
<td>true</td>
<td>Sets the nullable check on fields</td>
</tr>
+<tr>
+<td>snapshot-property.<em>custom-key</em></td>
+<td>null</td>
+<td>Adds an entry with custom-key and corresponding value in the snapshot
summary</td>
+</tr>
</tbody>
</table></div>
diff --git a/index.html b/index.html
index f0e7d91..741cbe4 100644
--- a/index.html
+++ b/index.html
@@ -460,5 +460,5 @@
<!--
MkDocs version : 1.0.4
-Build Date UTC : 2020-07-15 00:44:33
+Build Date UTC : 2020-07-27 16:18:02
-->
diff --git a/javadoc/0.9.0/search.js b/javadoc/0.9.0/search.js
index b773531..12f1d35 100644
--- a/javadoc/0.9.0/search.js
+++ b/javadoc/0.9.0/search.js
@@ -324,3 +324,7 @@ $(function() {
}
});
});
+
+getURLPrefix = function(ui) {
+ return '';
+};
diff --git a/reliability/index.html b/reliability/index.html
index c8848d1..fcca411 100644
--- a/reliability/index.html
+++ b/reliability/index.html
@@ -371,7 +371,7 @@
<p>Iceberg was designed to solve correctness problems that affect Hive tables
running in S3.</p>
<p>Hive tables track data files using both a central metastore for partitions
and a file system for individual files. This makes atomic changes to a
table’s contents impossible, and eventually consistent stores like S3 may
return incorrect results due to the use of listing files to reconstruct the
state of a table. It also requires job planning to make many slow listing
calls: O(n) with the number of partitions.</p>
<p>Iceberg tracks the complete list of data files in each <a
href="../terms#snapshot">snapshot</a> using a persistent tree structure. Every
write or delete produces a new snapshot that reuses as much of the previous
snapshot’s metadata tree as possible to avoid high write volumes.</p>
-<p>Valid snapshots in an Iceberg table are stored the table metadata file,
along with a reference to the current snapshot. Commits replace the path of the
current table metadata file using an atomic operation. This ensures that all
updates to table data and metadata are atomic, and is the basis for <a
href="https://en.wikipedia.org/wiki/Isolation_(database_systems)#Serializable">serializable
isolation</a>.</p>
+<p>Valid snapshots in an Iceberg table are stored in the table metadata file,
along with a reference to the current snapshot. Commits replace the path of the
current table metadata file using an atomic operation. This ensures that all
updates to table data and metadata are atomic, and is the basis for <a
href="https://en.wikipedia.org/wiki/Isolation_(database_systems)#Serializable">serializable
isolation</a>.</p>
<p>This results in improved reliability guarantees:</p>
<ul>
<li><strong>Serializable isolation</strong>: All table changes occur in a
linear history of atomic table updates</li>
diff --git a/sitemap.xml b/sitemap.xml
index 5f77afd..9afd2e1 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -2,72 +2,72 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
@@ -82,12 +82,12 @@
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
@@ -97,7 +97,7 @@
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
@@ -107,27 +107,27 @@
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
<loc>None</loc>
- <lastmod>2020-07-14</lastmod>
+ <lastmod>2020-07-27</lastmod>
<changefreq>daily</changefreq>
</url>
<url>
diff --git a/sitemap.xml.gz b/sitemap.xml.gz
index 926d322..2c4fefc 100644
Binary files a/sitemap.xml.gz and b/sitemap.xml.gz differ
diff --git a/spark/index.html b/spark/index.html
index c35d698..25802f8 100644
--- a/spark/index.html
+++ b/spark/index.html
@@ -854,6 +854,10 @@ data.writeTo("prod.db.table").create()
<h2 id="inspecting-tables">Inspecting tables<a class="headerlink"
href="#inspecting-tables" title="Permanent link">¶</a></h2>
<p>To inspect a table’s history, snapshots, and other metadata, Iceberg
supports metadata tables.</p>
<p>Metadata tables are identified by adding the metadata table name after the
original table name. For example, history for <code>db.table</code> is read
using <code>db.table.history</code>.</p>
+<div class="admonition note">
+<p class="admonition-title">Note</p>
+<p>As of Spark 3.0, the format of the table name for inspection
(<code>catalog.database.table.metadata</code>) doesn’t work with
Spark’s default catalog (<code>spark_catalog</code>). If you’ve
replaced the default catalog, you may want to use DataFrameReader API to
inspect the table. </p>
+</div>
<h3 id="history">History<a class="headerlink" href="#history" title="Permanent
link">¶</a></h3>
<p>To show table history, run:</p>
<pre><code class="sql">SELECT * FROM prod.db.table.history
