[
https://issues.apache.org/jira/browse/SQOOP-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14245958#comment-14245958
]
Veena Basavaraj edited comment on SQOOP-1878 at 12/14/14 4:00 PM:
------------------------------------------------------------------
[~gwenshap] I hope we are not writing software for so called "customers" but to
be semantically correct and do the things the right way.
If the requirement is to support a updateSubmissionAndGetLatest , that
completely get rid of GET api, it does make sense to me.
Second, I also encourage you to look at the RB, it is one line change to make a
API from GET to update ( apart from the unit tests), so I am appalled at your
argument of churn. Yes, failing to see a simple point and stretching this topic
this long is certainly a churn I did not expect
was (Author: vybs):
[~gwenshap] I hope we are not writing software for so called "customers" but to
be semantically correct and do the things the right way.
If the requirement is to support a updateSubmissionAndGetLatest , that
completely get rid of GET api, it does make sense to me.
> 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)
