[
https://issues.apache.org/jira/browse/OOZIE-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Virag Kothari updated OOZIE-1424:
---------------------------------
Attachment: OOZIE-1424.patch
Patch could not compile due to
/home/jenkins/jenkins-slave/workspace/oozie-trunk-precommit-build/client/src/main/java/org/apache/oozie/client/event/jms/JMSMessagingUtils.java:
type parameters of <T>T cannot be determined; no unique maximal instance
exists for type variable T with upper bounds
T,org.apache.oozie.client.event.message.EventMessage
Cannot find the root cause of this. The patch doesn't even change this file and
it compiles locally. Reattaching the patch to check.
> Improve SLA reliability on restart, fix bugs related to SLA and event
> generation
> --------------------------------------------------------------------------------
>
> Key: OOZIE-1424
> URL: https://issues.apache.org/jira/browse/OOZIE-1424
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Virag Kothari
> Assignee: Virag Kothari
> Fix For: trunk
>
> Attachments: OOZIE-1424.patch, OOZIE-1424.patch, OOZIE-1424.patch,
> OOZIE-1424.patch
>
>
> When Oozie restarts, the status and actual times of job in Summary beans
> should be the same as that in the Job beans. Also, the event processing info.
> should be correctly reflected.
> Bugs:
> Start time for Coordinator action event should be wf job start time
> Duration event processing is not correct when expected duration is not set or
> job finishes before starting
> No parent id in workflow job running event when spawned through coord
> Event queue pollbatch() should use List instead of Set to preserve ordering
--
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
