[
https://issues.apache.org/jira/browse/SQOOP-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241999#comment-14241999
]
Jarek Jarcec Cecho commented on SQOOP-1878:
-------------------------------------------
I see the point why {{GET}} request should not update structures based on the
user input - one should use {{POST}}, {{UPDATE}}, ... instead for such actions.
I don't think that it's entirely applicable here though. The reason is that I
believe that it's actually about the user and what is the API semantics. User
is trying to get status of his submission and that is why he is calling {{GET}}
status. That seems very natural to me as a person who is looking at the
specification.
On the implementation level, in order to answer that request if the job is
running Sqoop have to go to external system to get latest status. It doesn't
make much sense to return ~5 minute old status (and/or calling the update
thread more often). And we already have this updated information, so why not to
store it? To me it's more similar to a caching mechanism rather then doing
"update" operation.
> JobManager status method is a GET call and should not performa update
> operations
> --------------------------------------------------------------------------------
>
> Key: SQOOP-1878
> URL: https://issues.apache.org/jira/browse/SQOOP-1878
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
> Attachments: SQOOP-1878.patch
>
>
> JobManager status method is a GET call and should not performa update
> operations
> status () method on JobManager is get request from the rest API. it should
> not ever do an update.
> if we need more faster updates of job, then it is best to create a new action
> that can do it or reduce the updateSleep parameter to less than 5 minutes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
