sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-2916) When completing the TO part of a job, people cannot state custom SQL statement by any means
Date Tue, 03 May 2016 08:14:13 GMT

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

ASF GitHub Bot commented on SQOOP-2916:
---------------------------------------

Github user FuqiaoWang commented on the pull request:

    https://github.com/apache/sqoop/pull/19#issuecomment-216464764
  
    Thank you for your reply @afine, I have submitted my patch to:https://issues.apache.org/jira/browse/SQOOP-2916
.I would be very happy if you can review it.


> When completing the TO part of a job, people cannot state custom SQL statement by any
means
> -------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-2916
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2916
>             Project: Sqoop
>          Issue Type: Bug
>          Components: connectors/generic
>    Affects Versions: 1.99.6
>            Reporter: FuqiaoWang
>         Attachments: 2916.patch
>
>
> 1. When both TableName and SQL statement are provided, it reports the ’GENERIC_JDBC_CONNECTOR_0007("The
table name and the table sql cannot be specified together")' exception.
> 2. When only the SQL statement is provided, it reports the 'Both table name and SQL cannot
be specified' exception.
> The modification we have made is simply to allow the TableName and the SQL statement
can be input together and in this case, the SQL have the higher priority to be executed.



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

Mime
View raw message