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

Virag Kothari commented on OOZIE-1249:
--------------------------------------

+1..looks good..address the below comments before committing 

* Remove the below:
  {code}Below are the header properties on which JMS selectors can be applied 
{code}

* Can we have two separate sections for Job and SLA message body
   e.g MessageBody for Job events: List examples
       MessageBody for SLA events: List examples
 
*  Nominal Time in the context of independent workflow needs to be explained

* Can we show a sample email response?

* Mention alert-events is optional. Can we have notification-msg and 
upstream-apps in sla example?

* For AG_INSTALL docs:
  Can you check and see if we want to include some of the configs from 
EventHandlerService, JMSJobEventListener, MessageSerializer, 
SLAEmailEventListener, SLAService. 
Also, do we want to mention about the client config file for deserialization 
(oozie_client.properties )?
                
> SLA Documentation
> -----------------
>
>                 Key: OOZIE-1249
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1249
>             Project: Oozie
>          Issue Type: Sub-task
>    Affects Versions: trunk
>            Reporter: Mona Chitnis
>            Assignee: Mona Chitnis
>            Priority: Minor
>             Fix For: trunk
>
>         Attachments: OOZIE-1249-2.patch, OOZIE-1249-2.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Add new documentation to explain the new SLA monitoring feature and usage. 
> Patch also includes part Job Notifications doc (server installation related) 
> and changes in CoordinatorFunctionalSpec Schema Appendix part to order 
> Schemas latest first.
> In addition, the existing Oozie doc for Web Services API lacks examples for 
> using the SLA API i.e. retrieving records from SLA tables using sequence-id, 
> max limit and so on.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to