CaesarWangX opened a new issue, #11200: URL: https://github.com/apache/hudi/issues/11200
**_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** When using Spark Structured Streaming 3.4.1 with Hudi 0.14.0, it has been observed that the content of the **hoodie.properties** file remains unchanged within each micro batch. However, there are intermittent operations involving the creation and deletion of **hoodie.properties.backup** files, as well as the deletion and creation of **hoodie.properties files**. This behavior occasionally leads to failures in downstream query tasks. Such issues were not encountered with Hudi 0.11. (metastore.enable=false) **To Reproduce** Steps to reproduce the behavior: 1. 2. 3. 4. **Expected behavior** A clear and concise description of what you expected to happen. **Environment Description** * Hudi version : 0.14.0 * Spark version : 3.4.1 * Storage (HDFS/S3/GCS..) : S3 **Additional context** Upon comparing the source code of versions 0.14 and 0.11, the following differences were found: Hudi0.11.1: <img width="1025" alt="image" src="https://github.com/apache/hudi/assets/12985552/84ea1ff6-175d-4fcc-a514-8618242fa69e";> Hudi0.14.0: <img width="925" alt="image" src="https://github.com/apache/hudi/assets/12985552/3322351e-cbd3-44a6-a839-320f33ef61a1";> In Hudi 0.14, the condition “&& !metaClient.getTableConfig().getMetadataPartitions().isEmpty()” is missing from the logic, leading to 'shouldExecuteMetadataTableDeletion' always returning true. Consequently, the 'deleteMetadataTable' method is executed, resulting in recent modifications to the hoodie.properties file. However, in the case of “metastore.enable=false”, the result of “!metaClient.getTableConfig().getMetadataPartitions().isEmpty()” will always be false. Therefore, if this condition continues to exist, the current issue would not occur. **Stacktrace** ```Add the stacktrace of the error.``` -- 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]
