[
https://issues.apache.org/jira/browse/SQOOP-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14241357#comment-14241357
]
Veena Basavaraj commented on SQOOP-1869:
----------------------------------------
I will wait until the patch is uploaded. but it would be good to have this
logic of checking validSchema or not in one place, since I have seen this check
in many places.
It might be good to add this to a util as well, since other IDF implementations
can follow a standard.
> 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
>
> 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)
