[
https://issues.apache.org/jira/browse/OOZIE-929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Britt Cyr updated OOZIE-929:
----------------------------
Attachment: OOZIE-929.patch
Payload is the jobId, actionId, status
Topic is the jobId
> JMS in NotificationXCommand
> ---------------------------
>
> Key: OOZIE-929
> URL: https://issues.apache.org/jira/browse/OOZIE-929
> Project: Oozie
> Issue Type: New Feature
> Reporter: Britt Cyr
> Assignee: Britt Cyr
> Attachments: OOZIE-929.patch
>
>
> Currently for each notification, oozie uses an http connection to send a
> notification. Oozie could use a pub-sub model and a JMS message bus.
> 1. There are a few options for the topic. It could be user generated,
> although this would allow a lot of topics and inconsistent naming. It could
> be per job so users could subscribe to see the notifications of certain jobs.
> It could be done per user.
> 2. Ways to handle the large number of notifications since one notification
> could go to many subscribers. The payload of the notifications should be
> considered. Should it include everything about the action or should it only
> include important things like action id, action status, and time?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
