jackye1995 commented on code in PR #6600:
URL: https://github.com/apache/iceberg/pull/6600#discussion_r1145671053


##########
docs/table-migration.md:
##########
@@ -0,0 +1,129 @@
+---
+title: "Table Migration"
+url: table-migration
+weight: 400
+menu: main
+---
+<!--
+ - Licensed to the Apache Software Foundation (ASF) under one or more
+ - contributor license agreements.  See the NOTICE file distributed with
+ - this work for additional information regarding copyright ownership.
+ - The ASF licenses this file to You under the Apache License, Version 2.0
+ - (the "License"); you may not use this file except in compliance with
+ - the License.  You may obtain a copy of the License at
+ -
+ -   http://www.apache.org/licenses/LICENSE-2.0
+ -
+ - Unless required by applicable law or agreed to in writing, software
+ - distributed under the License is distributed on an "AS IS" BASIS,
+ - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ - See the License for the specific language governing permissions and
+ - limitations under the License.
+ -->
+# Hive and Spark Table Migration
+Iceberg supports converting Hive and Spark tables to Iceberg tables through 
Spark Procedures. For specific instructions on how to use the procedures, 
please refer to the [Table Migration via Spark 
Procedures](../spark-procedures/#table-migration) page.

Review Comment:
   Yes I agree we should point to the Spark procedure instead of repeat the 
information. I am expecting this dedicated page to explain more about how the 
migration works, including (1) how snapshot, migrate are different, (2) how to 
use snapshot/migrate + add files to continuously migrate a table, (3) how the 
migration works differently for Hive, Delta and in the future Hudi. 
   
   We can add some graphs and explain each case, and then point to the Spark 
procedure for actual usage of it. For Delta, we can add a section in java API 
documentation and point to that instead of a Spark procedure.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to