This is an automated email from the ASF dual-hosted git repository.
JingsongLi 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 87763fc5f9 [docs] Fix misleading DROP COLUMN doc for hive catalog
(#9538)
87763fc5f9 is described below
commit 87763fc5f93b46b7b8fd0fe2840a9c108a1489ee
Author: Pei Yu <[email protected]>
AuthorDate: Wed Sep 2 16:18:30 2026 +0800
[docs] Fix misleading DROP COLUMN doc for hive catalog (#9538)
---
docs/docs/flink/sql-alter.md | 12 +++++++++---
docs/docs/flink/sql-ddl.md | 2 +-
docs/docs/spark/sql-alter.md | 13 ++++++++++---
3 files changed, 20 insertions(+), 7 deletions(-)
diff --git a/docs/docs/flink/sql-alter.md b/docs/docs/flink/sql-alter.md
index 8c72a98eb6..f7cb3929fc 100644
--- a/docs/docs/flink/sql-alter.md
+++ b/docs/docs/flink/sql-alter.md
@@ -110,10 +110,16 @@ To drop a column in a row type, see [Changing Column
Type](#changing-column-type
:::
-In hive catalog, you need to ensure:
+:::warning
-1. disable `hive.metastore.disallow.incompatible.col.type.changes` in your
hive server
-2. or set `hadoop.hive.metastore.disallow.incompatible.col.type.changes=false`
in your paimon catalog.
+When using a `hive` catalog, this operation requires
`hive.metastore.disallow.incompatible.col.type.changes=false`
+to be set on the **Hive Metastore server** (in its `hive-site.xml`, then
restart HMS). Setting this key on the
+Paimon catalog (`WITH (...)`) or via a Flink SQL `SET` only configures the
*client-side* `HiveConf`; the value is
+**not** propagated to the remote Hive Metastore service over Thrift, so
setting it on the client has no effect.
+
+See [HIVE-17832](https://issues.apache.org/jira/browse/HIVE-17832) for the
historical discussion.
+
+:::
Otherwise this operation may fail, throws an exception like `The following
columns have types incompatible with the
existing columns in their respective positions`.
diff --git a/docs/docs/flink/sql-ddl.md b/docs/docs/flink/sql-ddl.md
index 654e477079..5e560d8210 100644
--- a/docs/docs/flink/sql-ddl.md
+++ b/docs/docs/flink/sql-ddl.md
@@ -108,7 +108,7 @@ You can define any default table options with the prefix
`table-default.` for ta
Also, you can create [FlinkGenericCatalog](./quick-start).
-> When using hive catalog to change incompatible column types through alter
table, you need to configure
`hive.metastore.disallow.incompatible.col.type.changes=false`. see
[HIVE-17832](https://issues.apache.org/jira/browse/HIVE-17832).
+> When using hive catalog to change incompatible column types through alter
table, you need to configure
`hive.metastore.disallow.incompatible.col.type.changes=false` on the **Hive
Metastore server** (in its `hive-site.xml`, then restart HMS). Setting this on
the Paimon catalog or via Flink SQL `SET` only configures the client-side
HiveConf and is not propagated to the remote HMS over Thrift. See
[HIVE-17832](https://issues.apache.org/jira/browse/HIVE-17832).
> If you are using Hive3, please disable Hive ACID:
>
diff --git a/docs/docs/spark/sql-alter.md b/docs/docs/spark/sql-alter.md
index 25d3ebd674..c348a7ea1b 100644
--- a/docs/docs/spark/sql-alter.md
+++ b/docs/docs/spark/sql-alter.md
@@ -174,10 +174,17 @@ The following SQL drops a nested column `f2` from a
struct type, which is the va
ALTER TABLE my_table DROP COLUMN v.value.f2;
```
-In hive catalog, you need to ensure:
+:::warning
-1. disable `hive.metastore.disallow.incompatible.col.type.changes` in your
hive server
-2. or `spark-sql --conf
spark.hadoop.hive.metastore.disallow.incompatible.col.type.changes=false` in
your spark.
+When using a `hive` catalog, this operation requires
`hive.metastore.disallow.incompatible.col.type.changes=false`
+to be set on the **Hive Metastore server** (in its `hive-site.xml`, then
restart HMS). Setting this key via
+`--conf
spark.hadoop.hive.metastore.disallow.incompatible.col.type.changes=false` only
configures the *client-side*
+`HiveConf`; the value is **not** propagated to the remote Hive Metastore
service over Thrift, so setting it on
+the client has no effect.
+
+See [HIVE-17832](https://issues.apache.org/jira/browse/HIVE-17832) for the
historical discussion.
+
+:::
Otherwise this operation may fail, throws an exception like `The following
columns have types incompatible with the
existing columns in their respective positions`.
