[iceberg-docs] branch asf-site updated: deploy: 52f500f4c79d9d32331781f588017307d7ba64f5

[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 0939458  deploy: 52f500f4c79d9d32331781f588017307d7ba64f5
0939458 is described below

commit 0939458c0cbcbf093e1e7977baea9d88c49d3113
Author: rdblue <rd...@users.noreply.github.com>
AuthorDate: Tue Jun 7 15:30:03 2022 +0000

    deploy: 52f500f4c79d9d32331781f588017307d7ba64f5
---
 multi-engine-support/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/multi-engine-support/index.html b/multi-engine-support/index.html
index a506c20..b43b019 100644
--- a/multi-engine-support/index.html
+++ b/multi-engine-support/index.html
@@ -14,7 +14,7 @@ When using Iceberg with these engines, the runtime jar is the only addition to t
 For example, to use Iceberg with Spark 3.2 and AWS integrations, <code>iceberg-spark-runtime-3.2_2.12</code> and AWS SDK dependencies are needed for the Spark installation.</p><p>Spark and Flink provide different runtime jars for each supported engine version.
 Hive 2 and Hive 3 currently share the same runtime jar.
 The runtime jar names and latest version download links are listed in <a href=./multi-engine-support/#current-engine-version-lifecycle-status>the tables below</a>.</p><h3 id=engine-version-lifecycle>Engine Version Lifecycle</h3><p>Each engine version undergoes the following lifecycle stages:</p><ol><li><strong>Beta</strong>: a new engine version is supported, but still in the experimental stage. Maybe the engine version itself is still in preview (e.g. Spark <code>3.0.0-preview</code>),  [...]
-Users should continuously upgrade their Flink version to stay up-to-date.</p><table><thead><tr><th>Version</th><th>Lifecycle Stage</th><th>Initial Iceberg Support</th><th>Latest Iceberg Support</th><th>Latest Runtime Jar</th></tr></thead><tbody><tr><td>1.11</td><td>End of Life</td><td>0.9.0</td><td>0.12.1</td><td><a href="https://search.maven.org/remotecontent?filepath=org/apache/iceberg/iceberg-flink-runtime/0.12.1/iceberg-flink-runtime-0.12.1.jar">iceberg-flink-runtime</a></td></tr><tr [...]
+Users should continuously upgrade their Flink version to stay up-to-date.</p><table><thead><tr><th>Version</th><th>Lifecycle Stage</th><th>Initial Iceberg Support</th><th>Latest Iceberg Support</th><th>Latest Runtime Jar</th></tr></thead><tbody><tr><td>1.11</td><td>End of Life</td><td>0.9.0</td><td>0.12.1</td><td><a href="https://search.maven.org/remotecontent?filepath=org/apache/iceberg/iceberg-flink-runtime/0.12.1/iceberg-flink-runtime-0.12.1.jar">iceberg-flink-runtime</a></td></tr><tr [...]
 This allows the Iceberg support to evolve with the engine.
 Projects such as <a href=https://trino.io/docs/current/connector/iceberg.html>Trino</a> and <a href=https://prestodb.io/docs/current/connector/iceberg.html>Presto</a> are good examples of such support strategy.</p><p>In this approach, an Iceberg version upgrade is needed for an engine to consume new Iceberg features.
 To facilitate engine development against unreleased Iceberg features, a daily snapshot is published in the <a href=https://repository.apache.org/content/repositories/snapshots/org/apache/iceberg/>Apache snapshot repository</a>.</p><p>If bringing an engine directly to the Iceberg main repository is needed, please raise a discussion thread in the <a href=../community>Iceberg community</a>.</p></div></div></body></html>
\ No newline at end of file