[
https://issues.apache.org/jira/browse/SQOOP-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089385#comment-15089385
]
Jarek Jarcec Cecho commented on SQOOP-2782:
-------------------------------------------
I think that restarting the minicluster if needed will be helpful so that we
don't have to create one test suite for each test that needs different
minicluster implementation. I however have two notes:
* We should restart the minicluster only if needed - e.g. if the next test
needs different minicluster then the last test
* We still need to introduce a way how each test can say "I need minicluster
class X" because we can't mess with {{System.properties}}. As I described on
the review for SQOOP-2758 hardcoding solution with {{System.properties}} will
make it impossible to override the minicluster from command line which we're
doing when we're running the existing tests on real cluster.
> Sqoop2: improvement SqoopInfrastructureProvider to support restart with
> different SqoopMiniCluster
> --------------------------------------------------------------------------------------------------
>
> Key: SQOOP-2782
> URL: https://issues.apache.org/jira/browse/SQOOP-2782
> Project: Sqoop
> Issue Type: Sub-task
> Components: sqoop2-test
> Reporter: Colin Ma
> Assignee: Colin Ma
> Fix For: 1.99.7
>
> Attachments: SQOOP-2782.001.patch
>
>
> Currently, SqoopInfrastructureProvider is started only once for test suite,
> and the default SqoopMiniCluster is JettySqoopMiniCluster. With the different
> test connectors, SqoopInfrastructureProvider should be started with different
> SqoopMiniCluster. A restart feature should be added to support this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
