[
https://issues.apache.org/jira/browse/SQOOP-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14287813#comment-14287813
]
Veena Basavaraj commented on SQOOP-2003:
----------------------------------------
Dont see why avro schema needs to be converted to sqoop schema when avro
obejcts are passed in avro IDF.
> Should not Schema be passed over the wire along with the IDF data?
> ------------------------------------------------------------------
>
> Key: SQOOP-2003
> URL: https://issues.apache.org/jira/browse/SQOOP-2003
> Project: Sqoop
> Issue Type: Bug
> Reporter: Veena Basavaraj
> Fix For: 2.0.0
>
>
> Should Schema be passed over the wire along with the IDF data?
> Related to matching as well, since we create matcher again in the
> SqoopOutputFormatExecutor
> {code}
> matcher = MatcherFactory.getMatcher(
> MRConfigurationUtils.getConnectorSchema(Direction.FROM,
> context.getConfiguration()),
> MRConfigurationUtils.getConnectorSchema(Direction.TO,
> context.getConfiguration()));
> toDataFormat = (IntermediateDataFormat<?>) ClassUtils.instantiate(context
> .getConfiguration().get(MRJobConstants.TO_INTERMEDIATE_DATA_FORMAT));
> // Using the TO schema since the SqoopDataWriter in the SqoopMapper
> encapsulates the toDataFormat
> toDataFormat.setSchema(matcher.getToSchema());
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
