[
https://issues.apache.org/jira/browse/SQOOP-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243433#comment-14243433
]
Veena Basavaraj commented on SQOOP-1878:
----------------------------------------
The current code does this
{code}
public MSubmission status(long jobId) {
Repository repository = RepositoryManager.getInstance().getRepository();
MSubmission mSubmission = repository.findLastSubmissionForJob(jobId);
if (mSubmission == null) {
return new MSubmission(jobId, new Date(),
SubmissionStatus.NEVER_EXECUTED);
}
// If the submission isin running state, let's update it
if (mSubmission.getStatus().isRunning()) {
update(mSubmission);
}
return mSubmission;
}
{code}
the premise of the ticket is not have updates in a GET api. So I am really
wondering what is the angle of cache and design wiki :)
> 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)
