[
https://issues.apache.org/jira/browse/SQOOP-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252356#comment-14252356
]
Hudson commented on SQOOP-1869:
-------------------------------
FAILURE: Integrated in Sqoop2-hadoop100 #740 (See
[https://builds.apache.org/job/Sqoop2-hadoop100/740/])
SQOOP-1869: Sqoop2: Expand schema matching to support two schemaless connectors
(abe:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=236b9ef9cc016e81dcd8122616f9014324c3973b)
* execution/mapreduce/src/test/java/org/apache/sqoop/job/TestMatching.java
*
connector/connector-sdk/src/main/java/org/apache/sqoop/connector/matcher/Matcher.java
* common/src/main/java/org/apache/sqoop/schema/ByteArraySchema.java
*
test/src/test/java/org/apache/sqoop/integration/connector/kafka/FromHDFSToKafkaTest.java
* test/src/main/java/org/apache/sqoop/test/testcases/KafkaConnectorTestCase.java
> 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,
> SQOOP-1869.2.patch, SQOOP-1869.4.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)
