[
https://issues.apache.org/jira/browse/SQOOP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502690#comment-13502690
]
Jan Mechtel commented on SQOOP-382:
-----------------------------------
Thanks for looking into this for me:
1) Sqoop executed with --username argument
Sqoop output: http://pastebin.com/sML5yL7w
12/11/22 11:07:25 ERROR sqoop.Sqoop: Got exception running Sqoop:
java.lang.RuntimeException: java.lang.RuntimeException:
com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open server "ns74c56t9"
requested by the login. The login failed.
java.lang.RuntimeException: java.lang.RuntimeException:
com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open server "ns74c56t9"
requested by the login. The login failed.
2) Username stored in JDBC URL
Sqoop output: http://pastebin.com/P2DZ7YqF
12/11/22 10:32:35 ERROR sqoop.Sqoop: Got exception running Sqoop:
java.lang.RuntimeException: java.lang.RuntimeException:
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user
'veodin_user'.
MR output >> in both cases the job doesn't show up in the task tracker, I
thought it would show up as job_201211201516_0089 based on this line from the
output:
12/11/22 10:32:35 INFO mapred.JobClient: Cleaning up the staging area
hdfs://overlord-datanode1:8020/user/overlord/.staging/job_201211201516_0089
Ideas?
> 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
