[
https://issues.apache.org/jira/browse/SQOOP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502968#comment-13502968
]
David Robson commented on SQOOP-382:
------------------------------------
It looks like you need to add the jar to the classpath - eg "java TestAzure -cp
./:./sqljdbc4.jar"
You also probably need to add the connection string to your Java code to
actually create the connection.
As for your problem - I asked a colleague who has used Sqoop on Azure before
and he gave me the following command line he used which worked successfully:
sqoop import --connect
"jdbc:sqlserver://YOUR_HOST.database.windows.net:1433;database=YOUR_DATABASE;user=YOUR_USER@YOUR_HOST;password=YOUR_PASSWORD"
--table YOUR_TABLE --target-dir YOUR_DIRECTORY --split-by YOUR_SPLIT_COLUMN
Could you try this command - so get rid of the connection parameters completely
- and specify the password in the URL just to see if it works?
>From my experience the connection parameters using the connection-param-file
>do not work (hence this bug) - so probably best to eliminate them all together.
> 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
