YannByron commented on code in PR #6225:
URL: https://github.com/apache/hudi/pull/6225#discussion_r934108604
##########
hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/spark/sql/hudi/command/CreateHoodieTableCommand.scala:
##########
@@ -62,12 +65,22 @@ case class CreateHoodieTableCommand(table: CatalogTable,
ignoreIfExists: Boolean
// check if there are conflict between table configs defined in hoodie
table and properties defined in catalog.
CreateHoodieTableCommand.validateTblProperties(hoodieCatalogTable)
- // init hoodie table
- hoodieCatalogTable.initHoodieTable()
+ val queryAsProp =
hoodieCatalogTable.catalogProperties.get(ConfigUtils.IS_QUERY_AS_RO_TABLE)
+ if (queryAsProp.isEmpty) {
Review Comment:
in a normal process, spark-hudi create and write a mor table, then create
ro/rt tables.
it's easy to support the scene you mentioned above. but i think a mor table
(a real table in filesystem, not necessary in metastore) is a prerequisite.
cc @XuQianJin-Stars WDYT?
--
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: commits-unsubscr...@hudi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
