You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Dian Fu (JIRA)" <ji...@apache.org> on 2015/09/08 05:05:45 UTC

[jira] [Commented] (SQOOP-2445) Sqoop2: Generic JDBC: Prevent use of tableColumns and sql at the same time

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

Dian Fu commented on SQOOP-2445:
--------------------------------

+1. 

> Sqoop2: Generic JDBC: Prevent use of tableColumns and sql at the same time
> --------------------------------------------------------------------------
>
>                 Key: SQOOP-2445
>                 URL: https://issues.apache.org/jira/browse/SQOOP-2445
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.7
>
>         Attachments: SQOOP-2445.patch
>
>
> We're supporting data retrieval with custom query. I see bunch of code around that is trying to solve situation when user enters both of custom query and specifies what columns he wants to transfer from that custom query. This seems to me as unnecessary complication as user can limit the column in the first place by specifying appropriate query. Hence I would like to prohibit this behavior.



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