[
https://issues.apache.org/jira/browse/SQOOP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502832#comment-13502832
]
Jan Mechtel commented on SQOOP-382:
-----------------------------------
Ok, basically you want to check that the other nodes can connect (so that we
are sure that not for example a dns errors causes this?) You assume correctly
that this is abit more complicated than mysql.
Could we instead put our cluster to only one master node and try to run sqoop
then, to rule out that problem source? (I didn't install cloudera sorry if
that's an easy question, I'll ask our admin too).
> 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
