sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Robson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-382) Connection parameters should be used on the mapper
Date Tue, 27 Nov 2012 00:46:58 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13504273#comment-13504273

David Robson commented on SQOOP-382:

Thanks Jarcec - for anyone using the Oracle Connector I have fixed it there as well: https://questmos.jira.com/browse/ORAOOP-18
Jan - The Microsoft connector may need to be updated as well - you might want to point them
at this issue so they can fix it as well.
> Connection parameters should be used on the mapper
> --------------------------------------------------
>                 Key: SQOOP-382
>                 URL: https://issues.apache.org/jira/browse/SQOOP-382
>             Project: Sqoop
>          Issue Type: Bug
>            Reporter: David Robson
>            Assignee: David Robson
>             Fix For: 1.4.3
>         Attachments: SQOOP-382.patch
> Currently you can specify connection parameters using --connection-param-file <properties-file>.
> This applies the connection parameters to the connection when generating the Sqoop code
- but the parameters are not passed down to the mapper.
> Instead of specifying a parameters file couldn't we have a comma seperated list that
could be specified on the command line or in sqoop-site.xml - that way it would be easier
to override the settings per job, and they would be passed down to the mappers. It would then
be simple to modify DBConfiguration.getConnection to read these.

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

View raw message