[DISCUSS] FALCON-1889 JMS user notification creates a topic per feed/process

[Venkat Ramachandran <me...@gmail.com>]

JIRA - https://issues.apache.org/jira/browse/FALCON-1889
Documentation - https://falcon.apache.org/Operability.html

Falcon creates a topic per feed/process for user notification. ActiveMQ is
the usual/default JMS provider used/integrated with Falcon and a topic
(with persistent consumer) in ActiveMQ will require a file handle and so
for larger number of feed/process combination, this approach is not
scalable eclipsed by resource constraints and leaks.

The other option is to have one topic but the map message to have feed or
process entity name. There is already a FALCON.ENTITY.TOPIC that meets the
requirement.

With that said, what is the use case and requirements around the user
notification with per feed/process JMS topic? I would propose to deprecate
it and add any other required info to the FALCON.ENTITY.TOPIC or create a
new one topic that satisfies all the needs.

Thanks
Venky

Re: [DISCUSS] FALCON-1889 JMS user notification creates a topic per feed/process

[Pallavi Rao <pa...@inmobi.com>]

+1 for the suggestion. If we use the right headers, JMS message selector
can be used by users to receive only messages of their interest.

On Wed, Apr 20, 2016 at 4:24 AM, Ying Zheng <yz...@hortonworks.com> wrote:

> Agree with Venky 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.
>
> Cheers,
> Ying
>
> On 4/19/16, 3:37 PM, "Venkat Ramachandran" <me...@gmail.com> wrote:
>
> >JIRA - https://issues.apache.org/jira/browse/FALCON-1889
> >Documentation - https://falcon.apache.org/Operability.html
> >
> >Falcon creates a topic per feed/process for user notification. ActiveMQ is
> >the usual/default JMS provider used/integrated with Falcon and a topic
> >(with persistent consumer) in ActiveMQ will require a file handle and so
> >for larger number of feed/process combination, this approach is not
> >scalable eclipsed by resource constraints and leaks.
> >
> >The other option is to have one topic but the map message to have feed or
> >process entity name. There is already a FALCON.ENTITY.TOPIC that meets the
> >requirement.
> >
> >With that said, what is the use case and requirements around the user
> >notification with per feed/process JMS topic? I would propose to deprecate
> >it and add any other required info to the FALCON.ENTITY.TOPIC or create a
> >new one topic that satisfies all the needs.
> >
> >Thanks
> >Venky
>
>

-- 
_____________________________________________________________
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.

Re: [DISCUSS] FALCON-1889 JMS user notification creates a topic per feed/process

[Ying Zheng <yz...@hortonworks.com>]

Agree with Venky 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.

Cheers,
Ying

On 4/19/16, 3:37 PM, "Venkat Ramachandran" <me...@gmail.com> wrote:

>JIRA - https://issues.apache.org/jira/browse/FALCON-1889
>Documentation - https://falcon.apache.org/Operability.html
>
>Falcon creates a topic per feed/process for user notification. ActiveMQ is
>the usual/default JMS provider used/integrated with Falcon and a topic
>(with persistent consumer) in ActiveMQ will require a file handle and so
>for larger number of feed/process combination, this approach is not
>scalable eclipsed by resource constraints and leaks.
>
>The other option is to have one topic but the map message to have feed or
>process entity name. There is already a FALCON.ENTITY.TOPIC that meets the
>requirement.
>
>With that said, what is the use case and requirements around the user
>notification with per feed/process JMS topic? I would propose to deprecate
>it and add any other required info to the FALCON.ENTITY.TOPIC or create a
>new one topic that satisfies all the needs.
>
>Thanks
>Venky