[doc] Move clone-tables to flink from migration

docs/content/migration/clone-tables.md → 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

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.
 

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

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