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 2012/12/23 18:52:13 UTC

[jira] [Assigned] (SQOOP-682) Use templating in job.etl classes

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

Jarek Jarcec Cecho reassigned SQOOP-682:
----------------------------------------

    Assignee: Jarek Jarcec Cecho
    
> Use templating in job.etl classes
> ---------------------------------
>
>                 Key: SQOOP-682
>                 URL: https://issues.apache.org/jira/browse/SQOOP-682
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 2.0.0
>
>
> Connector is specifying configuration objects and therefore we're passing generic objects to callbacks. Would be great if callback objects (Extractor, Loader, ...) would use java template mechanism to specify which configuration objects they are expecting to avoid unnecessary object casting.

--
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