You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/05/20 18:50:00 UTC

[jira] [Work logged] (BEAM-13608) Dynamic Topics management

     [ https://issues.apache.org/jira/browse/BEAM-13608?focusedWorklogId=772987&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-772987 ]

ASF GitHub Bot logged work on BEAM-13608:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/May/22 18:49
            Start Date: 20/May/22 18:49
    Worklog Time Spent: 10m 
      Work Description: aromanenko-dev commented on code in PR #17163:
URL: https://github.com/apache/beam/pull/17163#discussion_r878459304


##########
sdks/java/io/jms/src/main/java/org/apache/beam/sdk/io/jms/JmsIO.java:
##########
@@ -48,13 +49,18 @@
 import org.apache.beam.sdk.transforms.DoFn;
 import org.apache.beam.sdk.transforms.PTransform;
 import org.apache.beam.sdk.transforms.ParDo;

Review Comment:
   Was not it possible to avoid this breaking change? Like, add new functionality and keep a previous one  deprecated? 
   
   Just tested the latest Beam 2.39.0 RC2 and my job with JmsIO.write() failed to compile without additional code changes.





Issue Time Tracking
-------------------

    Worklog Id:     (was: 772987)
    Time Spent: 2.5h  (was: 2h 20m)

> 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: 2.5h
>  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)