[
https://issues.apache.org/jira/browse/SQOOP-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243593#comment-14243593
]
Veena Basavaraj edited comment on SQOOP-1878 at 12/12/14 2:09 AM:
------------------------------------------------------------------
There is no cache, it talks to the repository.findLastSubmissionForJob(jobId),
which is the database. So what is the cache here referred to ?
The focus should be to resolve issue at hand, rather than divulge into
tangential matters of urgency or not. Atleast from the previous comment I
assume having a GET api do database updates should be avoided.
Doing an update in a background thread seems perfectly fine. It is not a GET
api.
BTW, I also happen to send a patch with this.
was (Author: vybs):
There is no cache, it talks to the repository.findLastSubmissionForJob(jobId),
which is the database. So what is the cache here referred to ?
The focus should be to resolve issue at hand, rather than divulge into
tangential matters of urgency or not. Atleast from the previous comment I
assume having a GET api do database updates should be avoided.
BTW, I also happen to send a patch with this.
> 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)
