Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sqoop.apache.org
Date: Tue, 6 Dec 2016 12:56:00 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: dev@sqoop.apache.org
Message-ID: <JIRA.13025324.1480772479000.449626.1481028960932@Atlassian.JIRA>
In-Reply-To: <JIRA.13025324.1480772479000@Atlassian.JIRA>
References: <JIRA.13025324.1480772479000@Atlassian.JIRA> <JIRA.13025324.1480772479220@arcas>
Subject: [jira] [Commented] (SQOOP-3066) Introduce an option + env variable
 to enable/disable SQOOP-2737 feature
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 06 Dec 2016 12:56:05 -0000


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

ASF subversion and git services commented on SQOOP-3066:
--------------------------------------------------------

Commit bd51d987b81582692e300b99548365ff5d85bbaa in sqoop's branch refs/heads/trunk from [~maugli]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=bd51d98 ]

SQOOP-3069: Get OracleExportTest#testUpsertTestExport in line with SQOOP-3066

(Attila Szabo)


> Introduce an option + env variable to enable/disable SQOOP-2737 feature
> -----------------------------------------------------------------------
>
>                 Key: SQOOP-3066
>                 URL: https://issues.apache.org/jira/browse/SQOOP-3066
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.4.6
>            Reporter: Attila Szabo
>            Assignee: Attila Szabo
>            Priority: Critical
>             Fix For: 1.4.7
>
>         Attachments: SQOOP-3066.patch
>
>
> After [SQOOP-2737] several users ran into that their SQOOP commands are failing due to the fact the original commands were not phrased cases sensitive table/column/schema names in mind.
> There had been also another outcome of this feature, that the "--split-by" option does not accept Oracle functions anymore (e.g. MOD(col_name,4) ), as after correct escaping+quoting it would be handled by Oracle as a db col name, instead of an expression to evaluate.
> My goal here is to introduce an option to turn on/off the (fully proper and industry standard) escaping implemented in [SQOOP-2737], and also add an environment variable support for that, thus users would have the backward compatible fallback plan, and not changing their command.
> I do also plan to implement an argument for supporting split-by with database functions/expressions, and thus the escaping and the split-by expressions features would become independent.


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