[SUPPORT] Using MRO table and synchronizing to hive, Flink checkpoint failed, resulting in log files being unable to scroll to parquet files
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
**_Tips before filing an issue_**
- Have you gone through our [FAQs](https://hudi.apache.org/learn/faq/)?y
- Join the mailing list to engage in conversations and get faster support at dev-subscribe@hudi.apache.org.
- 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**
Using MRO table and synchronizing to hive, Flink checkpoint failed, resulting in log files being unable to scroll to parquet files

Using Flink to write a large amount of data to the Hudi table and synchronize it to Hive. Will occasional checkpoint failures result in the log file being unable to scroll to a parquet file, resulting in Hive querying less data than the Hudi table
**To Reproduce**
Steps to reproduce the behavior:
1. hive_sync.enabled=true
2.start flink checkpoint
3.
4.
**Expected behavior**
A clear and concise description of what you expected to happen.
**Environment Description**
* Hudi version : 1.0
* Flink version :1.15.2
* Hive version :3.1.3
* Hadoop version :
* Storage (HDFS/S3/GCS..) :
* Running on Docker? (yes/no) :
**Additional context**
Add any other context about the problem here.
**Stacktrace**
```Add the stacktrace of the error.```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the Flink checkpoint and Hive synchronization configuration described in the issue, including hive_sync.enabled=true and the listed Hudi, Flink, Hive, and Hadoop versions. Reproduce the checkpoint failure with the provided steps and collect the missing stack trace and storage details. Done means identifying why log files do not reach corresponding Parquet files and confirming that Hive exposes the complete Hudi data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering, stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100