[
https://issues.apache.org/jira/browse/FALCON-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582928#comment-14582928
]
Srikanth Sundarrajan commented on FALCON-1031:
----------------------------------------------
+1. Except for ....
Would prefer falcon specific properties in process definition to be explicitly
namespaced. for example "falcon.system.userJMSNotificationEnabled". In the past
we haven't done a good job and it is very hard to tell which of these
properties are interpreted and have special meaning in falcon and which of
these are actually user defined. Ideally they shouldn't even be defined
together. But that requires a lot of cleanup.
{code}
+ USER_JMS_NOTIFICATION_ENABLED("userJMSNotificationEnabled", "Is User
notification via JMS enabled?", false),
{code}
> Make post processing notifications to user topics optional
> ----------------------------------------------------------
>
> Key: FALCON-1031
> URL: https://issues.apache.org/jira/browse/FALCON-1031
> Project: Falcon
> Issue Type: Improvement
> Affects Versions: 0.7
> Reporter: Pallavi Rao
> Assignee: Pallavi Rao
> Priority: Minor
> Labels: reviewed
> Attachments: FALCON-1031-v2.patch, FALCON-1031-v3.patch,
> FALCON-1031.patch
>
>
> Currently, during post processing, messages are sent to Falcon system Topic
> and also to user topic (one per entity), by default. If the user is not
> interested in listening to job completion notifications, this is just
> additional load on the MQ.
> There should be an option to enable job completion notifications for users.
> To ensure backward compatibility, we should add to option to disable user
> notifications, may be, in the entity definition.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
