[jira] [Commented] (SQOOP-2916) When completing the TO part of a job, people cannot state custom SQL statement by any means
[
https://issues.apache.org/jira/browse/SQOOP-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15269393#comment-15269393
]
Abraham Fine commented on SQOOP-2916:
-
[~FuqiaoWang] this patch does not seem to cleanly apply to the sqoop2 branch
(we use this branch as the head of the sqoop2 project).
In addition, please rename the attached patch to SQOOP-2916.patch (this
filename pattern is needed for our automated testing to run).
Feel free to upload your patch to apache reviewboard
(https://reviews.apache.org/dashboard/) in addition to this jira and link it
here.. We like to use this tool for all but the smallest patches as it makes it
easier for the community to have a discussion on the code.
> 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)
[jira] [Commented] (SQOOP-2916) When completing the TO part of a job, people cannot state custom SQL statement by any means
[
https://issues.apache.org/jira/browse/SQOOP-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
