(hudi) branch asf-site updated: [HUDI-8629] Update Spark DML docs on schema evolution (#12635)

[sivabalan]

This is an automated email from the ASF dual-hosted git repository.

sivabalan pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hudi.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new d344710878b [HUDI-8629] Update Spark DML docs on schema evolution 
(#12635)
d344710878b is described below

commit d344710878bb11e4a6673179888be0e345ec7722
Author: Y Ethan Guo <ethan.guoyi...@gmail.com>
AuthorDate: Tue Jan 14 20:44:59 2025 -0800

    [HUDI-8629] Update Spark DML docs on schema evolution (#12635)
---
 website/docs/sql_dml.md                         | 6 ++++++
 website/versioned_docs/version-1.0.0/sql_dml.md | 6 ++++++
 2 files changed, 12 insertions(+)

diff --git a/website/docs/sql_dml.md b/website/docs/sql_dml.md
index 8b4200154ec..fd89ca8dfd4 100644
--- a/website/docs/sql_dml.md
+++ b/website/docs/sql_dml.md
@@ -23,6 +23,10 @@ INSERT INTO <table>
 SELECT <columns> FROM <source>;
 ```
 
+:::info
+`INSERT INTO` statement does not support evolving table schema. Please use DDL 
(e.g., `ALTER TABLE`) or Datasource write 
(`df.write.format("hudi")....save(basePath)`) to evolve table schema.
+:::
+
 :::note Deprecations
 From 0.14.0, `hoodie.sql.bulk.insert.enable` and `hoodie.sql.insert.mode` are 
deprecated. Users are expected to use `hoodie.spark.sql.insert.into.operation` 
instead.
 To manage duplicates with `INSERT INTO`, please check out [insert dup policy 
config](configurations#hoodiedatasourceinsertduppolicy).
@@ -123,6 +127,8 @@ ON <merge_condition>
 ```
 
 :::info
+`MERGE INTO` statement does not support evolving table schema. Please use DDL 
(e.g., `ALTER TABLE`) or Datasource write 
(`df.write.format("hudi")....save(basePath)`) to evolve table schema.
+
 `WHEN NOT MATCHED` clauses specify the action to perform if the values do not 
match.
 There are two kinds of `INSERT` clauses:
 1. `INSERT *` clauses require that the source table has the same columns as 
those in the target table.
diff --git a/website/versioned_docs/version-1.0.0/sql_dml.md 
b/website/versioned_docs/version-1.0.0/sql_dml.md
index 8b4200154ec..fd89ca8dfd4 100644
--- a/website/versioned_docs/version-1.0.0/sql_dml.md
+++ b/website/versioned_docs/version-1.0.0/sql_dml.md
@@ -23,6 +23,10 @@ INSERT INTO <table>
 SELECT <columns> FROM <source>;
 ```
 
+:::info
+`INSERT INTO` statement does not support evolving table schema. Please use DDL 
(e.g., `ALTER TABLE`) or Datasource write 
(`df.write.format("hudi")....save(basePath)`) to evolve table schema.
+:::
+
 :::note Deprecations
 From 0.14.0, `hoodie.sql.bulk.insert.enable` and `hoodie.sql.insert.mode` are 
deprecated. Users are expected to use `hoodie.spark.sql.insert.into.operation` 
instead.
 To manage duplicates with `INSERT INTO`, please check out [insert dup policy 
config](configurations#hoodiedatasourceinsertduppolicy).
@@ -123,6 +127,8 @@ ON <merge_condition>
 ```
 
 :::info
+`MERGE INTO` statement does not support evolving table schema. Please use DDL 
(e.g., `ALTER TABLE`) or Datasource write 
(`df.write.format("hudi")....save(basePath)`) to evolve table schema.
+
 `WHEN NOT MATCHED` clauses specify the action to perform if the values do not 
match.
 There are two kinds of `INSERT` clauses:
 1. `INSERT *` clauses require that the source table has the same columns as 
those in the target table.