[
https://issues.apache.org/jira/browse/SQOOP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502859#comment-13502859
]
Jarek Jarcec Cecho commented on SQOOP-382:
------------------------------------------
You're right, I would like you to check that you're able to connect from all
your nodes to you Azure database to verify that this is indeed Sqoop related
issue.
Reconfiguring you cluster seems weird to me (a lot of work for small gain).
What about putting together very simple java application (one class with
main()) that will open connection using JDBC and run simple query? That should
do the work and it inherently must be working on linux.
> 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
