[SUPPORT] Occur bucketid multiple cannot write data to the wrong partition
- 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/)?
- 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**
1. multiple write to a bucket index table for many times(100 or more)
2. occure bucketid multiple
3. cannot write to the parition
4. delete the partiton next write would success
A clear and concise description of the problem.
can refer to the issue https://github.com/apache/hudi/issues/7216
add a pr to support it : https://github.com/apache/hudi/pull/10898
**To Reproduce**
Steps to reproduce the behavior:
1. multiple write to a bucket index table for many times(100 or more)
2. occur bucketid multiple
3. cannot write to the parition
4. delete the partiton next write would success
**Expected behavior**
A clear and concise description of what you expected to happen.
**Environment Description**
* Hudi version : 0.14.0
* Spark version : 3.2.0
* Hive version :
* Hadoop version :
* Storage (HDFS/S3/GCS..) : HDFS
* 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 issue #7216 and pull request #10898, then reproduce repeated bucket-index writes on Hudi 0.14.0 with Spark 3.2.0 and HDFS. Done means repeated writes no longer produce duplicate bucket IDs or fail to write to the intended partition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- hadoop, java, spark
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100