[
https://issues.apache.org/jira/browse/SQOOP-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244151#comment-14244151
]
Gwen Shapira commented on SQOOP-1878:
-------------------------------------
I believe (from some experience), that the customers who care about GET not
doing an update (mostly those with security requirements), will care even more
about having a functional GET that doesn't do an update.
Just saying to users: if you want a functioning GET use the other API that
actually does an update, may be technically correct but not helpful.
-0 on changing GET to render it useless and adding a new API that everyone will
be forced to use. Its just churn.
I'd suggest parking the ticket until we have more clarity if the current REST
API actually a problem for anyone.
> 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)
