[
https://issues.apache.org/jira/browse/BEAM-13608?focusedWorklogId=757019&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-757019
]
ASF GitHub Bot logged work on BEAM-13608:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Apr/22 15:24
Start Date: 14/Apr/22 15:24
Worklog Time Spent: 10m
Work Description: rvballada commented on PR #17163:
URL: https://github.com/apache/beam/pull/17163#issuecomment-1099298646
@lukecwik I think it is ready for another round of review.
Thanks!
Issue Time Tracking
-------------------
Worklog Id: (was: 757019)
Time Spent: 1h 40m (was: 1.5h)
> 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:
> Time Spent: 1h 40m
> 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.1#820001)
