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

Gwen Shapira commented on SQOOP-1869:
-------------------------------------

RB: https://reviews.apache.org/r/29140/

Added the integration test. Couldn't sleep without it :)

> Sqoop2: Expand schema matching to support two schemaless connectors
> -------------------------------------------------------------------
>
>                 Key: SQOOP-1869
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1869
>             Project: Sqoop
>          Issue Type: Improvement
>            Reporter: Gwen Shapira
>            Assignee: Gwen Shapira
>             Fix For: 1.99.5
>
>         Attachments: SQOOP-1869.0.patch, SQOOP-1869.1.patch
>
>
> Currently the schema matches errors out if both FROM and TO connectors are 
> empty. This prevents us from supporting HDFS->Kafka.
> I suggest to change the code to support the following:
> 1. Empty schema will contain a single byte[] field with whatever the 
> connector writes into it.
> 2. As happens now, one connector is null and the other has a schema, the 
> schema that exists will be used to parse the data.
> 3. If we have two empty schemas, the TO connector will get a byte[] and 
> presumably know what to do with it.



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

Reply via email to