[
https://issues.apache.org/jira/browse/SQOOP-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694166#comment-14694166
]
Hudson commented on SQOOP-2442:
-------------------------------
FAILURE: Integrated in Sqoop2 #869 (See
[https://builds.apache.org/job/Sqoop2/869/])
SQOOP-2442: Sqoop2: Generic JDBC: Drop tests for specifying schema name and
custom SQL at the same time (abe:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=63c5dd57afacf63e77d3486974b4216b72d503cb)
*
connector/connector-generic-jdbc/src/test/java/org/apache/sqoop/connector/jdbc/TestToInitializer.java
> Sqoop2: Generic JDBC: Drop tests for specifying schema name and custom SQL at
> the same time
> -------------------------------------------------------------------------------------------
>
> Key: SQOOP-2442
> URL: https://issues.apache.org/jira/browse/SQOOP-2442
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.7
>
> Attachments: SQOOP-2442.patch
>
>
> We currently have [bunch of
> tests|https://github.com/apache/sqoop/blob/sqoop2/connector/connector-generic-jdbc/src/test/java/org/apache/sqoop/connector/jdbc/TestToInitializer.java#L195]
> that are verifying the case when user specifies custom schema and custom SQL
> query. This combination however doesn't make sense as we're not using schema
> option when using custom query and we're even having an explicit [check for
> that in the
> validator|https://github.com/apache/sqoop/blob/sqoop2/connector/connector-generic-jdbc/src/main/java/org/apache/sqoop/connector/jdbc/configuration/FromJobConfig.java#L66].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
