"Retain Orderning cannot be altered" exception on Pulsar Sink update
- Dominant language
- Java
- Stars
- 15.3k
- Forks
- 3.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 142
Description
**Describe the bug**
Exception message "Retain Orderning cannot be altered" is returned when updating a pulsar sink.
**To Reproduce**
1 - Create a sink in standalone mode
2 - Update the sink without modifying the retain oredering boolean
**Expected behavior**
Sink should be updated with the new configuration
**Additional context**
InfluxDB v2 PulsarIO Connector.
Contributor guide
Research direction
Start by reproducing the update in standalone mode with the InfluxDB v2 PulsarIO Connector, keeping the retain ordering boolean unchanged. Trace the sink update validation and compare the existing and new configurations; done means an unchanged retain ordering value no longer causes the exception and the sink updates successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100