[
https://issues.apache.org/jira/browse/SQOOP-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348048#comment-14348048
]
Hudson commented on SQOOP-2170:
-------------------------------
SUCCESS: Integrated in Sqoop-ant-jdk-1.6-hadoop200 #978 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop200/978/])
SQOOP-2170: MySQL specific tests are not properly cleaning up created tables
(abe:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=3a475c9694e208fd64e81441a8942ad8381de522)
* src/test/com/cloudera/sqoop/manager/DirectMySQLTest.java
* src/test/com/cloudera/sqoop/manager/JdbcMySQLExportTest.java
* src/test/org/apache/sqoop/manager/mysql/MySqlCallExportTest.java
* src/test/com/cloudera/sqoop/manager/DirectMySQLExportTest.java
* src/test/com/cloudera/sqoop/TestAllTables.java
> MySQL specific tests are not properly cleaning up created tables
> ----------------------------------------------------------------
>
> Key: SQOOP-2170
> URL: https://issues.apache.org/jira/browse/SQOOP-2170
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.5
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.4.6
>
> Attachments: SQOOP-2170.patch
>
>
> MySQL specific tests are mostly extending the usual HSQLDB tests. This is a
> bit of a problem, because the HSQLDB based tests are not properly cleaning up
> the created tables (they are dropped automatically as HSQLDB runs only
> in-memory engine). However MySQL have persisted store and hence we are
> creating mess in the database.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
