[ 
https://issues.apache.org/jira/browse/SQOOP-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13502086#comment-13502086
 ] 

Jarek Jarcec Cecho commented on SQOOP-382:
------------------------------------------

Hi Jan,
thank you very much for additional information. I would break your particular 
issue to several sub-issues:

1) Problematic "@" character.
What shell are you using? I've tried bash and I did not had any issues with 
putting password with "@" character. You can always put entire password to 
quotes (') or (") on most commonly available shells.

2) The content of connector file must be in form of key=value
You have invalid configuration of your Microsoft SQL Connector and as a result 
this connector is not loaded. Sqoop might work though as it will likely load 
build-in Microsoft SQL Server connector instead. You should fix your 
configuration in /usr/lib/sqoop/bin/../conf/managers.d/mssqoop-sqlserver to 
contain following format com.solar.earth.class.name=/path/to/jar .
                
> 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

Reply via email to