[
https://issues.apache.org/jira/browse/SQOOP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502141#comment-13502141
]
Jan Mechtel commented on SQOOP-382:
-----------------------------------
1) I've tried it with all three combinations (1st username in connection string
+ 2nd username in connection string and properties file + 3rd user name in
properties).
2) That's exactly what I've done now. btw you guessed the path correct. The
first error message is now gone but I still can't get past this message:
overlord@overlord-datanode1:~/Documents/hadoop/scripts/03_azure_sql$
./test_sqoop_azure_connection.sh
Enter password:
12/11/21 18:20:05 INFO SqlServer.MSSQLServerManagerFactory: Using Microsoft's
SQL Server - Hadoop Connector
12/11/21 18:20:05 INFO manager.SqlManager: Using default fetchSize of 1000
12/11/21 18:20:05 INFO tool.CodeGenTool: Beginning code generation
12/11/21 18:20:06 INFO manager.SqlManager: Executing SQL statement: SELECT TOP
1 * FROM [Unlocks]
12/11/21 18:20:06 INFO manager.SqlManager: Executing SQL statement: SELECT TOP
1 * FROM [Unlocks]
12/11/21 18:20:06 INFO orm.CompilationManager: HADOOP_HOME is /usr/lib/hadoop
Note: /tmp/sqoop-overlord/compile/25615050f948c94583e6659e87c39a58/Unlocks.java
uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
12/11/21 18:20:07 INFO orm.CompilationManager: Writing jar file:
/tmp/sqoop-overlord/compile/25615050f948c94583e6659e87c39a58/Unlocks.jar
12/11/21 18:20:08 INFO mapreduce.ImportJobBase: Beginning import of Unlocks
12/11/21 18:20:08 INFO manager.SqlManager: Executing SQL statement: SELECT TOP
1 * FROM [Unlocks]
12/11/21 18:20:09 WARN mapred.JobClient: Use GenericOptionsParser for parsing
the arguments. Applications should implement Tool for the same.
12/11/21 18:20:12 INFO mapred.JobClient: Cleaning up the staging area
hdfs://overlord-datanode1:8020/user/overlord/.staging/job_201211201516_0077
12/11/21 18:20:12 ERROR sqoop.Sqoop: Got exception running Sqoop:
java.lang.RuntimeException: java.lang.RuntimeException:
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user
'veodin_user'.
java.lang.RuntimeException: java.lang.RuntimeException:
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user
'veodin_user'.
Any other idea how I could escape the "@" or pass the properties file to the
mapreduce?
> 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
