Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sqoop.apache.org
Date: Tue, 14 Oct 2014 15:01:33 +0000 (UTC)
From: "Qian Xu (JIRA)" <jira@apache.org>
To: dev@sqoop.apache.org
Message-ID: <JIRA.12747595.1413139185000.263278.1413298893811@Atlassian.JIRA>
In-Reply-To: <JIRA.12747595.1413139185000@Atlassian.JIRA>
References: <JIRA.12747595.1413139185000@Atlassian.JIRA>
 <JIRA.12747595.1413139185049@arcas>
Subject: [jira] [Updated] (SQOOP-1581) Sqoop2: LoaderContext has the wrong
 Schema
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Qian Xu updated SQOOP-1581:
---------------------------
    Attachment: SQOOP-1581.3.patch

Thanks Abe for pointing that out. Only one line change is required.

> 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.2.patch, SQOOP-1581.3.patch, 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)