You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2013/02/05 20:50:15 UTC

[jira] [Updated] (SQOOP-864) Sqoop2: Introduce ETL context objects

     [ https://issues.apache.org/jira/browse/SQOOP-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Jarcec Cecho updated SQOOP-864:
-------------------------------------

    Attachment: bugSQOOP-864.patch
    
> Sqoop2: Introduce ETL context objects
> -------------------------------------
>
>                 Key: SQOOP-864
>                 URL: https://issues.apache.org/jira/browse/SQOOP-864
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.99.1
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.2
>
>         Attachments: bugSQOOP-864.patch
>
>
> I've came to a need to add new parameter into Extractor.extract and Loader.load methods. I've realized that doing so will break backward compatibility as both classes are part of public API for connectors. Right now it's not an issue as that API not stable yet, but it would be nice to create more generic approach that will allow us to extend it in the future without breaking backward compatibility.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira