You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@paimon.apache.org by lz...@apache.org on 2024/10/31 05:50:14 UTC
(paimon) branch master updated: [doc] Move clone-tables to flink from migration
This is an automated email from the ASF dual-hosted git repository.
lzljs3620320 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/paimon.git
The following commit(s) were added to refs/heads/master by this push:
new 734a0dc6e [doc] Move clone-tables to flink from migration
734a0dc6e is described below
commit 734a0dc6efaf3ba8cf23d67303184507a2a382a0
Author: Jingsong <ji...@gmail.com>
AuthorDate: Thu Oct 31 13:50:02 2024 +0800
[doc] Move clone-tables to flink from migration
---
docs/content/{migration => flink}/clone-tables.md | 4 ++--
docs/content/migration/upsert-to-partitioned.md | 4 ++++
docs/content/program-api/flink-api.md | 8 ++------
docs/content/program-api/java-api.md | 8 ++------
4 files changed, 10 insertions(+), 14 deletions(-)
diff --git a/docs/content/migration/clone-tables.md b/docs/content/flink/clone-tables.md
similarity index 99%
rename from docs/content/migration/clone-tables.md
rename to docs/content/flink/clone-tables.md
index 36355dd85..14075d57d 100644
--- a/docs/content/migration/clone-tables.md
+++ b/docs/content/flink/clone-tables.md
@@ -1,9 +1,9 @@
---
title: "Clone Tables"
-weight: 3
+weight: 94
type: docs
aliases:
-- /migration/clone-tables.html
+- /flink/clone-tables.html
---
<!--
Licensed to the Apache Software Foundation (ASF) under one
diff --git a/docs/content/migration/upsert-to-partitioned.md b/docs/content/migration/upsert-to-partitioned.md
index b82bc942a..d4fd00ae6 100644
--- a/docs/content/migration/upsert-to-partitioned.md
+++ b/docs/content/migration/upsert-to-partitioned.md
@@ -26,6 +26,10 @@ under the License.
# Upsert To Partitioned
+{{< hint warning >}}
+__Note:__ Only Hive Engine can be used to query these upsert-to-partitioned tables.
+{{< /hint >}}
+
The [Tag Management]({{< ref "maintenance/manage-tags" >}}) will maintain the manifests and data files of the snapshot.
A typical usage is creating tags daily, then you can maintain the historical data of each day for batch reading.
diff --git a/docs/content/program-api/flink-api.md b/docs/content/program-api/flink-api.md
index 7cf9d1932..6ecac3909 100644
--- a/docs/content/program-api/flink-api.md
+++ b/docs/content/program-api/flink-api.md
@@ -26,12 +26,8 @@ under the License.
# Flink API
-{{< hint warning >}}
-We do not recommend using programming API. Paimon is designed for SQL first, unless you are a professional Flink developer, even if you do, it can be very difficult.
-
-We strongly recommend that you use Flink SQL or Spark SQL, or simply use SQL APIs in programs.
-
-The following documents are not detailed and are for reference only.
+{{< hint info >}}
+If possible, recommend using Flink SQL or Spark SQL, or simply use SQL APIs in programs.
{{< /hint >}}
## Dependency
diff --git a/docs/content/program-api/java-api.md b/docs/content/program-api/java-api.md
index 97f4ac5ae..1bf0ce82f 100644
--- a/docs/content/program-api/java-api.md
+++ b/docs/content/program-api/java-api.md
@@ -26,12 +26,8 @@ under the License.
# Java API
-{{< hint warning >}}
-We do not recommend using the Paimon API naked, unless you are a professional downstream ecosystem developer, and even if you do, there will be significant difficulties.
-
-If you are only using Paimon, we strongly recommend using computing engines such as Flink SQL or Spark SQL.
-
-The following documents are not detailed and are for reference only.
+{{< hint info >}}
+If possible, recommend using computing engines such as Flink SQL or Spark SQL.
{{< /hint >}}
## Dependency