[commits the instant xxxxxx] error: Bad type on operand stack
- 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**
A clear and concise description of the problem.
**To Reproduce**
Steps to reproduce the behavior:
1. Flink SQL from kafka to hudi, using insert write type
2.deploy on k8s, storage with OSS
**Expected behavior**
A clear and concise description of what you expected to happen.
**Environment Description**
* Hudi version (0.14.0):
* Flink version (0.15.4):
* Hive version (3.1.2):
* Hadoop version (3.3.5):
* Storage (OSS) :
* Running on Docker? (yes) :
**Additional context**
Yarn + HDFS run successful, But k8s + OSS run error。
**Stacktrace**
```Add the stacktrace of the error.```

Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the listed Flink SQL Kafka-to-Hudi insert-write flow on Kubernetes with OSS, using the stated Hudi, Flink, Hive, and Hadoop versions. Compare it with the successful Yarn plus HDFS setup and collect the actual stacktrace, which is currently missing; done requires a reproducible diagnosis and verified resolution of the operand-stack error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java, kafka, kubernetes
- Domain
- data-engineering, devops, stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100