[
https://issues.apache.org/jira/browse/SQOOP-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250229#comment-14250229
]
Veena Basavaraj commented on SQOOP-1168:
----------------------------------------
[~gwenshap]
There are couple of question in this one paragraph so I will split it up
>> incremental jobs are fundamentally different?
Dont see incremental/ delta fetch / merge related info any different, than the
actual job config that asks shouldNullValuesBeAllowedInParitioColumn.
of course a job is expected to know what it will fetch and what it will write,
the configs presented will be presented to user when they do create job and
that info will be used in the connector when execution the job.
>>>as a user, I'd like to be able to know whether a job is inrcremental or
>>>not,?
Probably you meant a submission. The submission can hold that information.
this is already part of the proposal, that we need a API to expose the details
of the job submission including how many records were read. how many were
written, what was the boundary or last value, we can certainly add another
attribute that it was delta fetch and delta merge. And wil that be show job,
or show submission ?
Only submisison can tell if it did a delta fetch or delta merge and or both.
> Sqoop2: Delta Fetch/ Merge ( formerly called Incremental Import )
> -----------------------------------------------------------------
>
> Key: SQOOP-1168
> URL: https://issues.apache.org/jira/browse/SQOOP-1168
> Project: Sqoop
> Issue Type: Bug
> Reporter: Hari Shreedharan
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
>
> The formal design wiki is here
> https://cwiki.apache.org/confluence/display/SQOOP/Delta+Fetch+and+Merge+Design
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
