[
https://issues.apache.org/jira/browse/SQOOP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502826#comment-13502826
]
Jarek Jarcec Cecho commented on SQOOP-382:
------------------------------------------
Hi Jan,
I'm no Microsoft SQL Server on Azure expert, however from the error message
"Cannot open server "ns74c56t9" requested by the login. The login failed" I
would say that your entire username was transferred correctly as the the error
message contains server name that we thought is not transported.
Sqoop requires access to your database from all nodes in your hadoop cluster as
it's doing several data movements in parallel. We've seen similar issues with
for example MySQL where master node did have sufficient privileges, but all
slave nodes did not. Would you mind checking that you are able to connect to
your database from all nodes in your cluster? It's pretty easy task with the
MySQL, but I'm not sure how to do it for Microsoft SQL Server and I'm not sure
that Microsoft is shipping any linux compatible client.
> 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
