[
https://issues.apache.org/jira/browse/BIGTOP-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692062#comment-13692062
]
jay vyas commented on BIGTOP-1019:
----------------------------------
Great idea to decouple from mysql.
But, taking it further, since the base requirement of a sqoop ETL flow that a
jdbc driver is available for the data source --- maybe a mock JDBC data source
would be an even more appropriate way to implement the tests.
> Remove mysql requirement constraint from sqoop tests
> ----------------------------------------------------
>
> Key: BIGTOP-1019
> URL: https://issues.apache.org/jira/browse/BIGTOP-1019
> Project: Bigtop
> Issue Type: Improvement
> Components: Tests
> Affects Versions: 0.6.0
> Reporter: Konstantin Boudnik
> Fix For: 0.7.0
>
>
> Existing Sqoop tests contradict self-sufficiency of the integration testing
> paradigm. The tests require an axillary mysql server configuration. While it
> might be acceptable for an established infrastructure it clearly has the
> disadvantage for ad-hoc testing, where one needs to make sure that a
> specially configured mysql is available.
> Replacing mysql with H2 for the testing would solve the problem elegantly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
