[
https://issues.apache.org/jira/browse/HUDI-3898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523623#comment-17523623
]
Danny Chen commented on HUDI-3898:
----------------------------------
> it means that the user knows whether the table without the suffix is a _ro
> or _rt table
The user that writes/syncs the table and user that query the table may be
different ones. What i want to emphasize is that the contract view of Hoodie
now is:
'rt' means realtime table and 'ro' means read_optimized table, we can have
implicit strategy for example the table without suffix can be a 'ro' table.
If we only sync 'rt' table withput suffix, how does user know that this is a
'rt' table on the Hive side ?
> Mor table hive synchronization supports _ro or _rt table type selection and
> _rt table suffix skip configuration items
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: HUDI-3898
> URL: https://issues.apache.org/jira/browse/HUDI-3898
> Project: Apache Hudi
> Issue Type: Improvement
> Components: hive, meta-sync
> Reporter: Chuang Lee
> Priority: Major
> Fix For: 0.11.0
>
>
> Related links ：https://github.com/apache/hudi/issues/5327
> # The current mor table hive synchronization only supports the suffix
> skipping of the _ro table. Can it also support the suffix skipping
> configuration item of the _rt table? Because for some business scenarios,
> especially non-partitioned tables, in order to be consistent with the table
> names of existing businesses, some businesses only need the _ro table to skip
> the suffix, and some businesses only need the _rt table to skip the suffix,
> so do you consider adding configuration items? _rt table suffix.
> # The current mor table hive synchronization synchronizes the _ro table and
> the _rt table at the same time, which cannot be changed, but for some
> non-partitioned business scenarios, some only need to synchronize the _ro
> table or the _rt table to meet the requirements. If all are synchronized, it
> will bring extra cost, so consider adding configuration items to be more
> flexible to choose.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
