sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1581) Sqoop2: LoaderContext has the wrong Schema
Date Mon, 13 Oct 2014 15:59:34 GMT

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

Jarek Jarcec Cecho commented on SQOOP-1581:
-------------------------------------------

I think that we should not give the {{TO}} connector both schemes, because then different
connectors will implement the schema resolution differently which will lead to a different
behaviour depending on what connector combination is being used. I believe that Sqoop framework
should do the schema matching and resolution and just give {{TO}} connector one schema that
should be used.  The given schema might be {{TO}} schema if the {{TO}} connector has exposed
one or {{FROM}} if it did not.

> Sqoop2: LoaderContext has the wrong Schema
> ------------------------------------------
>
>                 Key: SQOOP-1581
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1581
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: from/to
>            Reporter: Abraham Elmahrek
>            Assignee: Qian Xu
>             Fix For: 1.99.4
>
>         Attachments: SQOOP-1581.patch
>
>
> {code}
>         if (!isTest) {
>           // Using the TO schema since the IDF returns data in TO schema
>           schema = ConfigurationUtils.getConnectorSchema(Direction.TO, conf);
>           ...
>         }
>         // Create loader context
>         LoaderContext loaderContext = new LoaderContext(subContext, reader, schema);
> {code}
> In some cases, the matcher will use the FROM schema. The loader should provide the FROM
schema in this case.



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

Mime
View raw message