You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Charles Wimmer (JIRA)" <ji...@apache.org> on 2014/03/13 02:51:50 UTC
[jira] [Updated] (OOZIE-1739) Actions not displayed on Web Service
API job endpoint
[ https://issues.apache.org/jira/browse/OOZIE-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Charles Wimmer updated OOZIE-1739:
----------------------------------
Description:
When querying the Web Services API on the job endpoint, the actions are not displayed. This is a regression from 3.3.2.
http://oozie.example.com:11000/oozie/v1/0000146-140304062937821-oozie-oozi-C
{noformat}
{
"total": 290,
"pauseTime": null,
"coordJobName": "Check-marketshare-logs",
"coordJobPath": "hdfs://nn.example.com:8020/user/flume/log_pipelineV11/coordinator_check.xml",
"timeZone": "UTC",
"frequency": "60",
"conf": "<configuration>\r\n <property>\r\n <name>output_base</name>\r\n <value>/data/combinedlogs</value>\r\n </property>\r\n <property>\r\n <name>startTime</name>\r\n <value>2014-03-01T00:00Z</value>\r\n </property>\r\n <property>\r\n <name>oozie.coord.application.path</name>\r\n <value>hdfs://nn.example.com:8020/user/flume/log_pipelineV11/coordinator_check.xml</value>\r\n </property>\r\n <property>\r\n <name>user.name</name>\r\n <value>flume</value>\r\n </property>\r\n <property>\r\n <name>mapreduce.job.user.name</name>\r\n <value>flume</value>\r\n </property>\r\n <property>\r\n <name>cluster</name>\r\n <value>clustername</value>\r\n </property>\r\n <property>\r\n <name>queueName</name>\r\n <value>production</value>\r\n </property>\r\n <property>\r\n <name>nameNode</name>\r\n <value>hdfs://nn.example.com:8020</value>\r\n </property>\r\n <property>\r\n <name>user_base</name>\r\n <value>/user/flume</value>\r\n </property>\r\n <property>\r\n <name>endTime</name>\r\n <value>2014-04-01T00:00Z</value>\r\n </property>\r\n <property>\r\n <name>jobTracker</name>\r\n <value>rm.example.com:8032</value>\r\n </property>\r\n <property>\r\n <name>appDir</name>\r\n <value>/user/flume/log_pipelineV11</value>\r\n </property>\r\n <property>\r\n <name>input_base</name>\r\n <value>/clusterlogs</value>\r\n </property>\r\n</configuration>",
"endTime": "Tue, 01 Apr 2014 00:00:00 GMT",
"executionPolicy": "FIFO",
"startTime": "Sat, 01 Mar 2014 00:00:00 GMT",
"timeUnit": "MINUTE",
"concurrency": 2,
"coordJobId": "0000146-140304062937821-oozie-oozi-C",
"lastAction": "Thu, 13 Mar 2014 02:00:00 GMT",
"status": "RUNNING",
"acl": null,
"mat_throttling": 12,
"timeOut": 120,
"nextMaterializedTime": "Thu, 13 Mar 2014 02:00:00 GMT",
"bundleId": null,
"toString": "Coordinator application id[0000146-140304062937821-oozie-oozi-C] status[RUNNING]",
"coordExternalId": null,
"group": null,
"user": "flume",
"consoleUrl": null,
"actions": [
]
}
{noformat}
was:
When querying the Web Services API on the job endpoint, the actions are not displayed. This is a regression from 3.3.2.
http://oozie.example.com:11000/oozie/v1/0000146-140304062937821-oozie-oozi-C
{
"total": 290,
"pauseTime": null,
"coordJobName": "Check-marketshare-logs",
"coordJobPath": "hdfs://nn.example.com:8020/user/flume/log_pipelineV11/coordinator_check.xml",
"timeZone": "UTC",
"frequency": "60",
"conf": "<configuration>\r\n <property>\r\n <name>output_base</name>\r\n <value>/data/combinedlogs</value>\r\n </property>\r\n <property>\r\n <name>startTime</name>\r\n <value>2014-03-01T00:00Z</value>\r\n </property>\r\n <property>\r\n <name>oozie.coord.application.path</name>\r\n <value>hdfs://nn.example.com:8020/user/flume/log_pipelineV11/coordinator_check.xml</value>\r\n </property>\r\n <property>\r\n <name>user.name</name>\r\n <value>flume</value>\r\n </property>\r\n <property>\r\n <name>mapreduce.job.user.name</name>\r\n <value>flume</value>\r\n </property>\r\n <property>\r\n <name>cluster</name>\r\n <value>clustername</value>\r\n </property>\r\n <property>\r\n <name>queueName</name>\r\n <value>production</value>\r\n </property>\r\n <property>\r\n <name>nameNode</name>\r\n <value>hdfs://nn.example.com:8020</value>\r\n </property>\r\n <property>\r\n <name>user_base</name>\r\n <value>/user/flume</value>\r\n </property>\r\n <property>\r\n <name>endTime</name>\r\n <value>2014-04-01T00:00Z</value>\r\n </property>\r\n <property>\r\n <name>jobTracker</name>\r\n <value>rm.example.com:8032</value>\r\n </property>\r\n <property>\r\n <name>appDir</name>\r\n <value>/user/flume/log_pipelineV11</value>\r\n </property>\r\n <property>\r\n <name>input_base</name>\r\n <value>/clusterlogs</value>\r\n </property>\r\n</configuration>",
"endTime": "Tue, 01 Apr 2014 00:00:00 GMT",
"executionPolicy": "FIFO",
"startTime": "Sat, 01 Mar 2014 00:00:00 GMT",
"timeUnit": "MINUTE",
"concurrency": 2,
"coordJobId": "0000146-140304062937821-oozie-oozi-C",
"lastAction": "Thu, 13 Mar 2014 02:00:00 GMT",
"status": "RUNNING",
"acl": null,
"mat_throttling": 12,
"timeOut": 120,
"nextMaterializedTime": "Thu, 13 Mar 2014 02:00:00 GMT",
"bundleId": null,
"toString": "Coordinator application id[0000146-140304062937821-oozie-oozi-C] status[RUNNING]",
"coordExternalId": null,
"group": null,
"user": "flume",
"consoleUrl": null,
"actions": [
]
}
> Actions not displayed on Web Service API job endpoint
> -----------------------------------------------------
>
> Key: OOZIE-1739
> URL: https://issues.apache.org/jira/browse/OOZIE-1739
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 4.0.0
> Reporter: Charles Wimmer
>
> When querying the Web Services API on the job endpoint, the actions are not displayed. This is a regression from 3.3.2.
> http://oozie.example.com:11000/oozie/v1/0000146-140304062937821-oozie-oozi-C
> {noformat}
> {
> "total": 290,
> "pauseTime": null,
> "coordJobName": "Check-marketshare-logs",
> "coordJobPath": "hdfs://nn.example.com:8020/user/flume/log_pipelineV11/coordinator_check.xml",
> "timeZone": "UTC",
> "frequency": "60",
> "conf": "<configuration>\r\n <property>\r\n <name>output_base</name>\r\n <value>/data/combinedlogs</value>\r\n </property>\r\n <property>\r\n <name>startTime</name>\r\n <value>2014-03-01T00:00Z</value>\r\n </property>\r\n <property>\r\n <name>oozie.coord.application.path</name>\r\n <value>hdfs://nn.example.com:8020/user/flume/log_pipelineV11/coordinator_check.xml</value>\r\n </property>\r\n <property>\r\n <name>user.name</name>\r\n <value>flume</value>\r\n </property>\r\n <property>\r\n <name>mapreduce.job.user.name</name>\r\n <value>flume</value>\r\n </property>\r\n <property>\r\n <name>cluster</name>\r\n <value>clustername</value>\r\n </property>\r\n <property>\r\n <name>queueName</name>\r\n <value>production</value>\r\n </property>\r\n <property>\r\n <name>nameNode</name>\r\n <value>hdfs://nn.example.com:8020</value>\r\n </property>\r\n <property>\r\n <name>user_base</name>\r\n <value>/user/flume</value>\r\n </property>\r\n <property>\r\n <name>endTime</name>\r\n <value>2014-04-01T00:00Z</value>\r\n </property>\r\n <property>\r\n <name>jobTracker</name>\r\n <value>rm.example.com:8032</value>\r\n </property>\r\n <property>\r\n <name>appDir</name>\r\n <value>/user/flume/log_pipelineV11</value>\r\n </property>\r\n <property>\r\n <name>input_base</name>\r\n <value>/clusterlogs</value>\r\n </property>\r\n</configuration>",
> "endTime": "Tue, 01 Apr 2014 00:00:00 GMT",
> "executionPolicy": "FIFO",
> "startTime": "Sat, 01 Mar 2014 00:00:00 GMT",
> "timeUnit": "MINUTE",
> "concurrency": 2,
> "coordJobId": "0000146-140304062937821-oozie-oozi-C",
> "lastAction": "Thu, 13 Mar 2014 02:00:00 GMT",
> "status": "RUNNING",
> "acl": null,
> "mat_throttling": 12,
> "timeOut": 120,
> "nextMaterializedTime": "Thu, 13 Mar 2014 02:00:00 GMT",
> "bundleId": null,
> "toString": "Coordinator application id[0000146-140304062937821-oozie-oozi-C] status[RUNNING]",
> "coordExternalId": null,
> "group": null,
> "user": "flume",
> "consoleUrl": null,
> "actions": [
> ]
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)