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

Cheolsoo Park commented on SQOOP-774:
-------------------------------------

+1. I verified that the issue is fixed. Will commit it soon.
                
> Sqoop2: exception is thrown when creating a connection object if 
> connectionString starts with an empty space
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-774
>                 URL: https://issues.apache.org/jira/browse/SQOOP-774
>             Project: Sqoop
>          Issue Type: Bug
>          Components: sqoop2-client
>    Affects Versions: 1.99.1
>            Reporter: Cheolsoo Park
>            Assignee: Jarek Jarcec Cecho
>            Priority: Blocker
>             Fix For: 1.99.1
>
>         Attachments: bugSQOOP-774.patch
>
>
> To reproduce it, do the following:
> {code}
> sqoop:000> create connection --cid 1
> Creating connection for connector with id 1
> Please fill following values to create new connection object
> Name: blah
> Configuration configuration
> JDBC Driver Class: blah
> JDBC Connection String:  blah <--- an empty space before blah
> Username: blah
> Password: blah
> JDBC Connection Properties: 
> There are currently 0 values in the map:
> entry# 
> Security related configuration options
> Max connections: 
> log4j:WARN No appenders could be found for logger 
> (org.apache.sqoop.utils.ClassUtils).
> log4j:WARN Please initialize the log4j system properly.
> log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
> info.
> Exception has occurred during processing command 
> Server has returned exception: Exception: java.lang.Throwable Message: 
> VALIDATION_0002:Usage of missing field - Field connectionString is not 
> present in 
> org.apache.sqoop.connector.jdbc.configuration.ConnectionConfiguration
> {code}

--
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