falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ying Zheng (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FALCON-1889) Falcon JMS created too many topics - one per process/feed
Date Tue, 19 Apr 2016 22:55:25 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15248847#comment-15248847
] 

Ying Zheng edited comment on FALCON-1889 at 4/19/16 10:55 PM:
--------------------------------------------------------------

Agree with [~venkat.ramachan] that creating one topic per entity is not scalable as the total
number of entities can grow large.

One suggestion: ActiveMQ provides JMS message selectors, so the user can receive only messages
whose headers and properties match the selector. If we add entity name and tag in the message
property, the user can use it to filter the message based on name or tags with one consistent
topic.


was (Author: yzheng-hortonworks):
Agree with [~venkat.ramachan] that creating one topic per entity is not scalable as the
total number of entities can grow large.

One suggestion: ActiveMQ provides JMS message selectors, so the user can
receive only messages whose headers and properties match the selector. If
we add entity name and tag in the message property, the user can use it to
filter the message based on name or tags with one consistent topic.

> Falcon JMS created too many topics - one per process/feed
> ---------------------------------------------------------
>
>                 Key: FALCON-1889
>                 URL: https://issues.apache.org/jira/browse/FALCON-1889
>             Project: Falcon
>          Issue Type: Bug
>          Components: general
>            Reporter: Venkatesan Ramachandran
>            Assignee: Venkatesan Ramachandran
>
> Per https://falcon.apache.org/Operability.html, Falcon creates a topic for feed/process
to publish messages. 
> If there are large number of feeds/processes, it would create too many JMS topics that
will be un-managable.  If this is true, this needs to be fixed and all the messages to be
published to one well-know topic that external applications can consume from.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message