[
https://issues.apache.org/jira/browse/BEAM-13608?focusedWorklogId=762622&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-762622
]
ASF GitHub Bot logged work on BEAM-13608:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Apr/22 23:19
Start Date: 26/Apr/22 23:19
Worklog Time Spent: 10m
Work Description: lukecwik commented on PR #17163:
URL: https://github.com/apache/beam/pull/17163#issuecomment-1110338200
The next step would be to add a failure/retry policy so that the user can
choose which messages are retried and which go to the failure pcollection. Some
users would rather they fail the bundle and be retried without needing to look
at the failure pcollection. @rvballada is this something you can add?
Issue Time Tracking
-------------------
Worklog Id: (was: 762622)
Time Spent: 2h 20m (was: 2h 10m)
> Dynamic Topics management
> -------------------------
>
> Key: BEAM-13608
> URL: https://issues.apache.org/jira/browse/BEAM-13608
> Project: Beam
> Issue Type: Improvement
> Components: io-java-jms
> Reporter: Vincent BALLADA
> Assignee: Vincent BALLADA
> Priority: P2
> Labels: assigned:
> Fix For: 2.39.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> JmsIO write function is able to publish messages to topics with static names:
> company/employee/id/1234567.
> Some AMQP/JMS broker provides the ability to publish to dynamic topics like:
> company/employee/id/\{employeeId}
> If we want to handle that with Apache Beam JmsIO, we must create a branch per
> employeeId, which is not suitable for a company with thousand of employee, or
> other similat use cases.
> The JmsIO write function should provide the ability to handle dynamic topics.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
