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

Sqoop QA bot commented on SQOOP-1821:
-------------------------------------

Testing file 
[SQOOP-1821-v1.patch|https://issues.apache.org/jira/secure/attachment/12691841/SQOOP-1821-v1.patch]
 against branch sqoop2 took 0:00:09.238002.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to apply patch (exit code 1):
{code}<stdin>:50: trailing whitespace.
   * 
error: cannot apply binary patch to 
'core/src/test/resources/test-connector.jar' without full index line
error: core/src/test/resources/test-connector.jar: patch does not apply
error: cannot apply binary patch to 
'core/src/test/resources/test-non-connector.jar' without full index line
error: core/src/test/resources/test-non-connector.jar: patch does not apply
{code}

{color:green}SUCCESS:{color} Clean was successful

Console output is available 
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/916/console].

This message is automatically generated.

> External connector loading in Sqoop2
> ------------------------------------
>
>                 Key: SQOOP-1821
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1821
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.5
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>             Fix For: 1.99.5
>
>         Attachments: SQOOP-1821-v1.patch, SQOOP-1821.patch
>
>
> Edit this wiki to begin with
> https://cwiki.apache.org/confluence/display/SQOOP/Setting+up+Sqoop+2#SettingupSqoop2-InstallinganewconnectortoSqoop2
> Also, add the same to the .rst of need be
> relevant code that loads all connectors 
> https://github.com/apache/sqoop/blob/sqoop2/core/src/main/java/org/apache/sqoop/connector/ConnectorManagerUtils.java#L44
> NOTE : External contributors had issues with getting a new sqoop connector 
> working seamlessly with the Sqoop2. They had to do some hacks to include this 
> new jar into the class path. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to