[
https://issues.apache.org/jira/browse/SQOOP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501763#comment-13501763
]
Jan Mechtel commented on SQOOP-382:
-----------------------------------
Sure, my bad.
overlord@overlord-datanode1:~/Documents/hadoop/scripts/03_azure_sql$ cat
test_sqoop_azure_connection.sh
/usr/lib/sqoop/bin/sqoop import -P --connect
'jdbc:sqlserver://ns74c5q6t9.database.windows.net' --connection-param-file
sqoop_azure_connection.properties --table Unlocks --target-dir
/data/azure/dbo_unlocks
overlord@overlord-datanode1:~/Documents/hadoop/scripts/03_azure_sql$ cat
sqoop_azure_connection.properties
username=us@ns74c5q6t9
database=veodin
currentSchema=dbo
I put the username inside the connection-param-file because otherwise it would
not work with the @ , maybe one way around the issue would be to escape the @
(I tried {@}) ?
Also I was thinking that maybe because of the first error:
ERROR sqoop.ConnFactory: Error loading ManagerFactory information from file
/usr/lib/sqoop/bin/../conf/managers.d/mssqoop-sqlserver: java.io.IOException:
the content of connector file must be in form of key=value
The parameters are not passed correctly because the default ConnectionFactory
is used?
Thanks for taking the time to look at this. I would have posted a question if I
hadn't found this bug report which seemed to match.
> 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
