[
https://issues.apache.org/jira/browse/SQOOP-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Ma updated SQOOP-2782:
----------------------------
Attachment: SQOOP-2782.001.patch
[~jarcec], this JIRA is for the problem found in SQOOP-2758. The root cause is
the sqoop server start with the incorrect sqoopMiniCluster. I think the
simplicity way is adding a method to restart sqoop with different
sqoopMiniCluster. The restart can be called in @BeforeClass, @BeforeMethod, and
so on.
There is no review board for this minor change.
Does it make sense for this problem?
> 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)
