[
https://issues.apache.org/jira/browse/SQOOP-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251753#comment-14251753
]
Jarek Jarcec Cecho commented on SQOOP-1168:
-------------------------------------------
Very nice proposal [~vybs], thank you for working on this big topic.
It seems that the current proposal is suggesting to introduce concept of "last
value" that will be stored using different means than the configuration object.
Do we think that having one value is sufficient for every connector? I'm
thinking about more advanced connectors - I don't have a good example in my
mind right now, but I can imagine that we will have connector that want to
store more information for incremental then just "last value" (unless the last
value is compound). Another question that pop up in my mind is how we're going
to enable users to change the "last value" in case that they will need to re-do
parts of the import? It's not something that I see users doing daily, but I did
see several situations where reseting the "last value" to some early state made
sense. Wild solution that I came up with (not sure how good/bad it is), would
be to let the connector update the Configuration object after the import with
the current "last values". That would be easy as user could edit it the same
way and it would enable arbitrary information in the config being updated. The
downsides is that now the connector would have ability to change the config
which is concept that we don't have in Sqoop yet.
> 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)
