Robert Kanter created OOZIE-1784:
------------------------------------
Summary: notificationMessage and upstreamApps fields missing from
SLA Rest API
Key: OOZIE-1784
URL: https://issues.apache.org/jira/browse/OOZIE-1784
Project: Oozie
Issue Type: Bug
Affects Versions: 4.0.1, 4.0.0
Reporter: Robert Kanter
An SLA notification includes the "notificationMessage" and "upstreamApps"
fields when going through JMS. However, if you look at it via the REST API,
those fields are missing. According to the documentation (and in being
consistent with the JMS message), they should be there.
Documentation:
https://oozie.apache.org/docs/4.0.1/DG_SLAMonitoring.html#Scenario_1:_Workflow_Job_Start_Miss
{code}
{ id : "000056-1238791320234-oozie-joe-W"
parentId : "000001-1238791320234-oozie-joe-C@8"
appType : "WORKFLOW_JOB"
msgType : "SLA"
appName : "my-sla-app"
slaStatus : "IN_PROCESS"
eventStatus : "START_MISS"
user: "joe"
nominalTime: "2013-16-22T05:00Z"
expectedStartTime: "2013-16-22T05:10Z" <-- (should start by this time)
actualStartTime: "2013-16-22T05:30Z" <-- (20 min late relative to expected
start)
expectedEndTime: "2013-16-22T05:40Z" <-- (should end by this time)
actualEndTime: null
expectedDuration: 15
actualDuration: null
notificationMessage: "My Job has encountered an SLA event!"
upstreamApps: "dependent-app-1, dependent-app-2"
}
{code}
When I actually use the API:
{code}
$ curl
http://HOST:11000/oozie/v2/sla/?filter=id=0000012-140403181356152-oozie-oozi-W
| python -mjson.tool
{
"slaSummaryList": [
{
"actualDuration": 69218,
"actualEnd": 1396911136000,
"actualStart": 1396911067000,
"appName": "MapReduce-SLA",
"appType": "WORKFLOW_JOB",
"expectedDuration": 1800000,
"expectedEnd": 1396506600000,
"expectedStart": 1396505400000,
"id": "0000012-140403181356152-oozie-oozi-W",
"jobStatus": "SUCCEEDED",
"lastModified": 1396911163000,
"nominalTime": 1396504800000,
"slaStatus": "MISS",
"user": "admin"
}
]
}
{code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
