VitoMakarevich opened a new issue, #10088: URL: https://github.com/apache/hudi/issues/10088
**_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** A clear and concise description of the problem. **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.13.1 * Spark version : 3.4.0(AWS) 3.3.x * Hive version : * Hadoop version : * Storage (HDFS/S3/GCS..) : * Running on Docker? (yes/no) : no **Additional context** Please read https://issues.apache.org/jira/browse/HUDI-7034. Copy here: Starting from 0.13.1 `spark.catalog.refreshTable` works incorrectly. In 0.12.3 it works ok. Reproduction is [here](https://github.com/VitoMakarevich/hudi-incremental-issue/blob/master/src/main/scala/com/example/hudi/HudiRefreshBug.scala). What is happening - there is a `BaseHoodieTableFileIndex` class in Hudi - it's saved in spark plan once the table is created. When I call to refresh, the respective method `doRefresh` is called. This method reloads the metadata view, and list of partitions, but now it does not refresh the list of files in partitions - this causes a bug that partitions are stuck at the first file version. So - updates are not picked up and after a couple of commits based on cleaner settings - Spark starts to throw a file not found exception. More precisely - it looks to be broken in [this commit ](https://github.com/apache/hudi/commit/34b226c0cba7ff022eb8c02246f46c5f9cbe7ec5) I can try to provide a fix. **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]
