[
https://issues.apache.org/jira/browse/SQOOP-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251787#comment-14251787
]
Veena Basavaraj commented on SQOOP-1168:
----------------------------------------
[~jarcec] you are right that last_value has been used as a placeholder to
explain the output, it can be any thing that the connector wants to store and
it can be any type. Hence the suggestion to extend the current counters to a
more generic output table and have a TYPE field there.
Good question [~jarcec]: There is an API part I suggested in wiki, (see the
Take 2 design and the storing output section) where the SQ_JOB_INPUT table
would store this value per config, per direction, per job and we have the
CONFIG API SQOOP_1516 that would allow editing of them if need be. If we have a
requirement to edit these values, we can do the same with the JOB_OUPUT API.
Again impelmentation details on what we will call it but it should very easy to
do that, it is just a key/value pair with TYPE
> 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)
