[
https://issues.apache.org/jira/browse/SQOOP-2441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14705249#comment-14705249
]
Sqoop QA bot commented on SQOOP-2441:
-------------------------------------
Testing file
[SQOOP-2441.patch|https://issues.apache.org/jira/secure/attachment/12751519/SQOOP-2441.patch]
against branch sqoop2 took 0:00:37.474217.
{color:red}Overall:{color} -1 due to an error(s), see details below:
{color:green}SUCCESS:{color} Clean was successful
{color:green}SUCCESS:{color} Patch applied correctly
{color:green}SUCCESS:{color} Patch add/modify test case
{color:green}SUCCESS:{color} License check passed
{color:red}ERROR:{color} failed to build with patch (exit code 1,
[report|https://builds.apache.org/job/PreCommit-SQOOP-Build/1606/artifact/patch-process/install.txt])
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/1606/console].
This message is automatically generated.
> Sqoop2: Generic JDBC: Drop support for specifying custom query when exporting
> data
> ----------------------------------------------------------------------------------
>
> Key: SQOOP-2441
> URL: https://issues.apache.org/jira/browse/SQOOP-2441
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.7
>
> Attachments: SQOOP-2441.patch, SQOOP-2441.patch
>
>
> In the early days of the development we've added new feature to the JDBC
> connector that enabled user to specify custom query to insert the data -
> similarly as user can specify custom query to select data. I see several
> problems with the feature:
> * It's actually not working at all right now because we're not able to
> [generate schema from the custom
> query|https://github.com/apache/sqoop/blob/sqoop2/connector/connector-generic-jdbc/src/main/java/org/apache/sqoop/connector/jdbc/GenericJdbcToInitializer.java#L66].
> * It doesn't allow us to do any batching as we're doing in Sqoop 1 when we're
> putting several rows into the same query which will hurt performance.
> * I did not see any real request for this feature from users
> Hence I would like to propose dropping this unfinished/non-working feature
> all together. Any thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
