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 32d7bf6  Deployed 349e8e304 with MkDocs version: 1.0.4
32d7bf6 is described below

commit 32d7bf6a53fc9e374875bb55e2873650ba7d4ea9
Author: Ryan Blue <[email protected]>
AuthorDate: Tue Jul 14 16:22:54 2020 -0800

    Deployed 349e8e304 with MkDocs version: 1.0.4
---
 index.html       |   2 +-
 sitemap.xml.gz   | Bin 225 -> 225 bytes
 spark/index.html |   3 ++-
 3 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index 9afbb06..49e5cf8 100644
--- a/index.html
+++ b/index.html
@@ -460,5 +460,5 @@
 
 <!--
 MkDocs version : 1.0.4
-Build Date UTC : 2020-07-15 00:21:05
+Build Date UTC : 2020-07-15 00:22:54
 -->
diff --git a/sitemap.xml.gz b/sitemap.xml.gz
index c42c7b2..a80e78a 100644
Binary files a/sitemap.xml.gz and b/sitemap.xml.gz differ
diff --git a/spark/index.html b/spark/index.html
index c91f4c9..50cc90c 100644
--- a/spark/index.html
+++ b/spark/index.html
@@ -795,10 +795,11 @@ WHERE ts &gt;= '2020-05-01 00:00:00' and ts &lt; 
'2020-06-01 00:00:00'
 </ul>
 </li>
 </ul>
+<p>The v1 DataFrame <code>write</code> API is still supported, but is not 
recommended.</p>
 <div class="admonition warning">
 <p class="admonition-title">Warning</p>
 <p>When writing with the v1 DataFrame API in Spark 3, use 
<code>saveAsTable</code> or <code>insertInto</code> to load tables with a 
catalog.
-Using <code>format("iceberg")</code> loads an isolated table reference that 
will not refresh tables used by queries.</p>
+Using <code>format("iceberg")</code> loads an isolated table reference that 
will not automatically refresh tables used by queries.</p>
 </div>
 <h3 id="appending-data">Appending data<a class="headerlink" 
href="#appending-data" title="Permanent link">&para;</a></h3>
 <p>To append a dataframe to an Iceberg table, use <code>append</code>:</p>

Reply via email to