[
https://issues.apache.org/jira/browse/SQOOP-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14249355#comment-14249355
]
Gwen Shapira commented on SQOOP-1168:
-------------------------------------
To clarify my recommendation for storing last_value and other information we
want to preserve between job runs:
I don't recommend using the submission table itself (which has rather strict
structure as [~vybs] noted), but rather store the information in the counters
table (SQ_COUNTER_SUBMISSION), which has many-to-one relation with submission
(each submission can have multiple counters).
You can store as many counters as you want, and last_value will certainly work.
This way we have good history and no need to modify history.
I think the current APIs around submission handle counters, but we'll probably
need to add something to get counters from the previous job run (single SQL in
Oracle and PG, but probably not in MySQL or Derby).
> 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)
