[
https://issues.apache.org/jira/browse/SQOOP-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Veena Basavaraj updated SQOOP-1798:
-----------------------------------
Description:
Since we will store the last value we should able to query this anytime.
Additional requirement is to support editing this value as well, each
submission will have a output object that will be retrieved and presented in
this API.
was:
Since we will store the last value ( or more precisely the predicate
information in the from config) we should able to query this anytime.
There is already a ticket to expose configs as first class / top level
entities, so this will allow the user to query the last value that was used in
the prev job run.
We surely need a job group Id to retrieve the last value, say we store this in
FromConfig of the job, before creating a new incremental job if I need the last
value, I need to give some id ...should this be a prev job Id? or should we
have a group Id, to associate all the incrementals in one group.
Summary: Support a API/ command line utility to retrieve the last value
or any JOB_OUTPUT (was: Support a API/ command line utility to retrieve the
last value ( probably via the FromConfig ..))
> Support a API/ command line utility to retrieve the last value or any
> JOB_OUTPUT
> --------------------------------------------------------------------------------
>
> Key: SQOOP-1798
> URL: https://issues.apache.org/jira/browse/SQOOP-1798
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
>
> Since we will store the last value we should able to query this anytime.
> Additional requirement is to support editing this value as well, each
> submission will have a output object that will be retrieved and presented in
> this API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
