[
https://issues.apache.org/jira/browse/SQOOP-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14243632#comment-14243632
]
Jarek Jarcec Cecho commented on SQOOP-1878:
-------------------------------------------
I'm just wondering, would assumption that nobody is currently blocked by this
JIRA correct, [~vybs]?
I believe that the proposal to create some sort of a cache is because we would
prefer not to provide stale information to the client (the goal #2) and at the
same time we don't want to run the update thread every second or so (the goal
#3), so that you can have something like:
{code}
if(submission.lastlyUpdated().isAcceptablyOldInformation()) {
return submission;
} else {
return SubmissionEngine.getFreshUpdateAndReturnItToClient();
}
{code}
> 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)
