[
https://issues.apache.org/jira/browse/SQOOP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502112#comment-13502112
]
Jan Mechtel commented on SQOOP-382:
-----------------------------------
1) The "@" is in the username it's a Azure MS SQL specific thing where you need
to connect with the username: <username>@<host>. When I put this directly into
the connection string the server would deny authorization to "<username>" that
lead me to the assumption that everything behind the @ get's ignored. When I
put it into the connection.properties I pass this barrier at least.
2) OK I will go back and check the configuration of the MSSQL_SQOOP_CONNECTOR,
I might have missed a step. With "com.solar.earth.class.name=/path/to/jar " you
mean I should put the file to the connector jar as value for the MSSQL Scoop
Connector?
> 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
