You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/06/23 02:34:24 UTC
[jira] [Commented] (BIGTOP-1019) Remove mysql requirement
constraint from sqoop tests
[ https://issues.apache.org/jira/browse/BIGTOP-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040314#comment-14040314 ]
jay vyas commented on BIGTOP-1019:
----------------------------------
I've got this working in BIGTOP-1222, marking as subsumed......
The strategy i went with was to use hsql to launch an embedded db at runtime, and then launch a sqoop job in the test.
After the *Sqoop* job runs the embedded hsql server is stopped and shut down.
> 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
> Assignee: Mikhail Antonov
> Fix For: 0.8.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 was sent by Atlassian JIRA
(v6.2#6252)