leosanqing commented on issue #9687: URL: https://github.com/apache/hudi/issues/9687#issuecomment-1715247880
> @leosanqing I comprehend your point, but having a distinct "ro" table registered in Hive can enhance the user experience, and both tables can still be queried. In my perspective, a table should provide consistent outputs regardless of the configuration, as this can prevent confusion. I don't believe there would be a significant increase in overhead by registering one more schema in the catalog There is only one table on HMS when creating a table using flink or spark, but there are two tables during synchronization. You can use flink or spark to query the rt table. It supports three types of queries, read optimization/snapshot/increment, but hive can only have two types. Personally, I think this aspect may cause some trouble for novices. It would be better if it could be unified. -- 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]
