[
https://issues.apache.org/jira/browse/OOZIE-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14389424#comment-14389424
]
Jacob Tolar commented on OOZIE-2157:
------------------------------------
i think that's a pretty typical RESTful convention - adding a new job to the
jobs collection would be a POST to /jobs.
that said, i do think it's confusing that there are 2 separate endpoints. as
far as i can tell, there's no real reason /jobs and /job can't be combined into
a single /jobs endpoint (except that you'd need to bump the api version to v3
to avoid compatibility issues).
POST /jobs - unchanged
GET /jobs - unchanged
GET /jobs/<jobid> - same behavior as /job/<jobid>
> Oozie job submit calls jobsServlet ( not jobServelt) to submit job
> ------------------------------------------------------------------
>
> Key: OOZIE-2157
> URL: https://issues.apache.org/jira/browse/OOZIE-2157
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
>
> {code}
> JobSubmit(Properties conf, boolean start) {
> super("POST", RestConstants.JOBS, "", (start) ?
> prepareParams(RestConstants.ACTION_PARAM,
> RestConstants.JOB_ACTION_START) : prepareParams());
> this.conf = notNull(conf, "conf");
> }
> {code}
> Where other job operation goes to jobServelt.
> Does anyone know reason behind this?
> In-fact jobServlet doesn't have any method to accept job submission.
> It confusion for people who uses web-service to interact with Oozie.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
