Limess opened a new issue, #8114: URL: https://github.com/apache/hudi/issues/8114
**_Tips before filing an issue_** - Have you gone through our [FAQs](https://hudi.apache.org/learn/faq/)? - 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** After running an insert using `insert_overwrite_table`, partitions which no longer exist in the new input data are not removed by the Hive Sync This is on Hudi 0.12.1, but I'm fairly sure this issue still exists on 0.13.0 - this change: https://github.com/apache/hudi/pull/6662 fixes this behaviour for `delete_partition` operations, but doesn't add any handling for `insert_overwrite_table`. I'd be happy to be proven otherwise. **To Reproduce** Steps to reproduce the behavior: 1. Create a new Hudi table using input data with two partitions 2. Insert into the table using `INSERT_OVERWRITE_TABLE` with input data containing 1/2 of the original partitions 3. Run HiveSyncTool 4. Check the Hive partitions. Both partitions still exist **Expected behavior** I'd expect the partition which was not inserted to be removed **Environment Description** * Hudi version : 0.12.1 * Spark version : 3.3.1 * Hive version : AWS Glue * Hadoop version : * Storage (HDFS/S3/GCS..) : S3 * Running on Docker? (yes/no) : no **Additional context** Running on EMR 0.6.9 -- 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]
