You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2015/10/21 22:29:27 UTC

[jira] [Resolved] (SQOOP-2003) Should not Schema be passed over the wire along with the IDF data?

     [ https://issues.apache.org/jira/browse/SQOOP-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Jarcec Cecho resolved SQOOP-2003.
---------------------------------------
    Resolution: Not A Problem

We're already passing the schema inside the MR job, so resolving.

> 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)