[
https://issues.apache.org/jira/browse/SQOOP-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286903#comment-14286903
]
Veena Basavaraj commented on SQOOP-1782:
----------------------------------------
Did not turn out to be a simple fix.
1. The client is now fixed to set the jname query parameter correctly,
2. We also fallback on jobId, if the name is not given. We prefer jobName as
the api suggests. But we will support the jobId as well.
> Sqoop2: Method call SqoopClient.getSubmissionsForJob(long) will return
> submissions for all jobs
> -----------------------------------------------------------------------------------------------
>
> Key: SQOOP-1782
> URL: https://issues.apache.org/jira/browse/SQOOP-1782
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.4
> Reporter: Jarek Jarcec Cecho
> Assignee: Veena Basavaraj
> Labels: newbie
> Fix For: 1.99.5
>
> Attachments: SQOOP-1782-v1.patch, SQOOP-1782.patch
>
>
> I've noticed that method call
> {{[SqoopClient.getSubmissionsForJob(long)|https://github.com/apache/sqoop/blob/sqoop2/client/src/main/java/org/apache/sqoop/client/SqoopClient.java#L542]}}
> returns submission objects for *all* jobs instead of the given one. Looking
> into
> {{[SubmissionRequestHandler|https://github.com/apache/sqoop/blob/sqoop2/server/src/main/java/org/apache/sqoop/handler/SubmissionRequestHandler.java#L51]}}
> I'm assuming that this is caused by the fact that {{SqoopClient}} is sending
> the job id as part of the URL ({{v1/submissions/$jid}}) whereas the
> {{SubmissionRequestHandler}} is looking for URL parameter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
