You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2013/06/24 06:33:19 UTC

[jira] [Commented] (BIGTOP-1019) Remove mysql requirement constraint: existing Sqoop tests contradict self-sufficiency of the integration testing paradigm

    [ https://issues.apache.org/jira/browse/BIGTOP-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691698#comment-13691698 ] 

Konstantin Boudnik commented on BIGTOP-1019:
--------------------------------------------

To elaborate on this a little... 
H2 is a single jar full scale DB server. It can be started as a separate JVM process or programmatically, e.g. from test setup method. It can keep the DB in memory, which suits the purpose perfectly, as the test won't need to clean up after itself.

Here's even better part - H2 can pretend to be anything between mysql to Postgress, with stuff like mssql, oracle and else in between.
                
> Remove mysql requirement constraint: existing Sqoop tests contradict self-sufficiency of the integration testing paradigm
> -------------------------------------------------------------------------------------------------------------------------
>
>                 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
>
>
> Current Sqoop 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