Support LookupOptions.MAX_RETRIES for flink connector
- Dominant language
- Java
- Stars
- 2.1k
- Forks
- 625
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 97
Description
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
### Motivation
Support LookupOptions.MAX_RETRIES for flink connector. Currently, Fluss doesn't support connector level
retry. The option 'client.lookup.max-retries' is only for dealing with the `RetriableException` return by server not all exceptions.
### Solution
_No response_
### Anything else?
_No response_
### Willingness to contribute
- [ ] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Flink connector handling of LookupOptions.MAX_RETRIES and compare it with the existing client.lookup.max-retries behavior. Trace how connector-level retries handle exceptions, then verify the change with tests covering retries beyond server-returned RetriableException cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- stream-processing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100