CodeCooker17 opened a new issue, #5327:
URL: https://github.com/apache/hudi/issues/5327

   **_Tips before filing an issue_**
   
   - Have you gone through our [FAQs](https://hudi.apache.org/learn/faq/)? yes
   
   - Join the mailing list to engage in conversations and get faster support at 
[email protected]. 
   
   - If you have triaged this as a bug, then file an [issue] 
(https://issues.apache.org/jira/projects/HUDI/issues) directly.
   
   **Describe the problem you faced**
   
   1. 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.
   2. 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?
   
   **To Reproduce**
   
   **Expected behavior**
   
   A clear and concise description of what you expected to happen.
   
   **Environment Description**
   
   * Flink version : 1.13.2
   
   * Hudi version : 0.10.1
   
   * Spark version : 3.1.2
   
   * Hive version : 2.1.1
   
   * Hadoop version : 2.6.5
   
   * Storage (HDFS/S3/GCS..) : hdfs
   
   * Running on Docker? (yes/no) : no
   
   


-- 
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]

Reply via email to