[
https://issues.apache.org/jira/browse/FALCON-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255883#comment-15255883
]
Pallavi Rao commented on FALCON-1926:
-------------------------------------
The JMS broker selector can be applied on JMS message headers only and not
body. Since we don't set any particular message headers for the message sent in
post processing action, we will not be able to apply the selector, as long as
we support sending messages in post-processing action.
Two options:
1. Deprecate and remove messages being sent from post-processing action and
apply selectors.
2. Add some headers for messages sent from post-processing action, so we can
apply selectors.
Prefer option 1. There is already an option to turn-off messages from
post-processing in startup.properties.
> Filter out effectively non-falcon related JMS messages from Oozie
> -----------------------------------------------------------------
>
> Key: FALCON-1926
> URL: https://issues.apache.org/jira/browse/FALCON-1926
> Project: Falcon
> Issue Type: Improvement
> Components: messaging
> Affects Versions: trunk
> Reporter: Venkatesan Ramachandran
> Assignee: Venkatesan Ramachandran
>
> Enabling Oozie JMS will flood the falcon JMS topic with both falcon and
> non-falcon submitted workflow status notifications, where as Falcon is only
> interested in the messages for the workflows it submitted.
> Using JMS selector, only relevant messages need to be retrieved and processed
> further.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
