[
https://issues.apache.org/jira/browse/SQOOP-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662580#comment-14662580
]
Jarek Jarcec Cecho commented on SQOOP-2446:
-------------------------------------------
Thanks for the review [~dian.fu]. It's actually an intention here. As we don't
have a standalone REST end point for the callback, I'm "reusing" the usual job
status call. But at the same time I would like to know on the server side
whether the request is coming from "real" user or whether it's the notification
callback. As we're currently ignoring all URL segments between {{v1/job/}} and
{{$JOB_ID/status}} I've decided to insert a {{notification}}} keyword to see in
the logs that this has been a call from execution engine. I know that it's not
perfect though - the right solution would be to have standalone notification
end point.
> Sqoop2: Fix incorrect notification URL for execution engine
> -----------------------------------------------------------
>
> Key: SQOOP-2446
> URL: https://issues.apache.org/jira/browse/SQOOP-2446
> Project: Sqoop
> Issue Type: Bug
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.7
>
> Attachments: SQOOP-2446.patch
>
>
> While looking into the {{NullPointerException}} in SQOOP-2439 I've noticed
> that we've changed the REST interface in incompatible way without changing
> the notification URL accordingly.
> The original way was to use {{job/status/$ID}} whereas the new format is
> {{job/$ID/status}}. We should change the notification URL accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
