[SPARK-55645][SQL] Add serdeName to CatalogStorageFormat#54467
[SPARK-55645][SQL] Add serdeName to CatalogStorageFormat#54467tagatac wants to merge 1 commit intoapache:masterfrom
Conversation
|
I'm not experienced in the use of |
|
@pan3793 |
@sarutak I'm not sure it's a good idea, we generally use table/serde properties to store custom info. Was it already used in any famous project? Either ASF project or commercial project. But meanwhile, I also don't see a reason to disallow that. I'm neutral on this change. |
|
@pan3793 I don't know existing OSS projects that uses serdeName but this field is arbitrarily set by end users through Hive's metastore API. So, if existing Hive table has serdeName set by users and it's not feasible to modify table properties, serdeName can be helpful. |
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/interface.scala
Outdated
Show resolved
Hide resolved
sql/hive/src/test/scala/org/apache/spark/sql/hive/HiveMetastoreCatalogSuite.scala
Outdated
Show resolved
Hide resolved
a1f49db to
70508e5
Compare
|
+0. I have no more comments. |
|
Merged to |
What changes were proposed in this pull request?
serdeNametoorg.apache.spark.sql.catalyst.catalog.CatalogStorageFormat.DESCRIBE EXTENDEDqueries.Why are the changes needed?
SerDeInforeturned by the Hive Metastore API.Before this change:
After this change:
Does this PR introduce any user-facing change?
Yes, developers can now access
CatalogStorageFormat.serdeName, representing the Hive Metastore API fieldSerDeInfo.name, when interacting with Spark representations of Hive tables.How was this patch tested?
DESCRIBE EXTENDEDrun viaspark-shellreturns "Serde Name" properly for a Hive table with a Serde name:Was this patch authored or co-authored using generative AI tooling?
No.
This contribution is my original work, and I license the work to the Spark project under the project’s open source license.