From dev-return-13924-apmail-sqoop-dev-archive=sqoop.apache.org@sqoop.apache.org Mon Oct 13 15:44:34 2014 Return-Path: X-Original-To: apmail-sqoop-dev-archive@www.apache.org Delivered-To: apmail-sqoop-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9FA37177A5 for ; Mon, 13 Oct 2014 15:44:34 +0000 (UTC) Received: (qmail 15153 invoked by uid 500); 13 Oct 2014 15:44:34 -0000 Delivered-To: apmail-sqoop-dev-archive@sqoop.apache.org Received: (qmail 15113 invoked by uid 500); 13 Oct 2014 15:44:34 -0000 Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sqoop.apache.org Delivered-To: mailing list dev@sqoop.apache.org Received: (qmail 15100 invoked by uid 99); 13 Oct 2014 15:44:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Oct 2014 15:44:34 +0000 Date: Mon, 13 Oct 2014 15:44:34 +0000 (UTC) From: "Qian Xu (JIRA)" To: dev@sqoop.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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.patch Simply provide both {{FROM}} and {{TO}} schema for {{LoaderContext}}. How to use it should be decided by programmer. > 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)