[
https://issues.apache.org/jira/browse/SQOOP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502978#comment-13502978
]
David Robson commented on SQOOP-382:
------------------------------------
It looks to me like your problem might be with the Microsoft connector itself -
I am not sure where to get support for that as I am not familiar with it - but
seems like a bug they should fix.
Anyway - in regards to SQOOP-382 the connection parameters don't work - should
this be fixed in 1.x branch or should we leave it to 2.x? If it's not going to
be fixed in 1.x should we at least update the documentation warning people is
does not work?
> 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
>
> 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
