[
https://issues.apache.org/jira/browse/SQOOP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502989#comment-13502989
]
David Robson commented on SQOOP-382:
------------------------------------
I actually looked into this a fair bit when I raised it - I think the easiest
way is to just make it a Configuration parameter - then you can use the
standard Hadoop Configuration object to get the array of connection parameters.
Part of the problem with this for Sqoop 1.x is each connector has to implement
it - so while it can be fixed in Sqoop - it won't work in say the Microsoft
connector or the Quest one. Of course if it's fixed I can fix the Quest
connector...
Let me know if this feature is desirable - seeing as I'd have to fix OraOop
anyway I could fix it in Sqoop at the same time and submit a patch.
> 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: Jarek Jarcec Cecho
> Fix For: 1.4.3
>
>
> 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
