Amraneze opened a new issue, #24971:
URL: https://github.com/apache/beam/issues/24971
### What happened?
When using `JmsIO` for publishing messages, we found out that messages are
not being published when the connection is closed due to any reason (Network,
Broker down ...). Even though we have the option to get failed published
messages we don't have a way to have a retry policy.
````java
var failedPublishedMessages =
messages.apply(getWriter(sinkOptions)).getFailedMessages();
failedPublishedMessages.apply(REPUBLISH_FAILED_MESSAGE_NAME,
getWriter(sinkOptions));
return PDone.in(cdpMessages.getPipeline());
````
>Note: the function `getWriter` returns JMS writer `JmsIO.Write<Message>`
### Issue Priority
Priority: 1 (data loss / total loss of function)
### Issue Components
- [ ] Component: Python SDK
- [ ] Component: Java SDK
- [ ] Component: Go SDK
- [ ] Component: Typescript SDK
- [X] Component: IO connector
- [ ] Component: Beam examples
- [ ] Component: Beam playground
- [ ] Component: Beam katas
- [ ] Component: Website
- [ ] Component: Spark Runner
- [ ] Component: Flink Runner
- [ ] Component: Samza Runner
- [ ] Component: Twister2 Runner
- [ ] Component: Hazelcast Jet Runner
- [ ] Component: Google Cloud Dataflow Runner
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
