[
https://issues.apache.org/jira/browse/PHOENIX-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15402380#comment-15402380
]
Loknath Priyatham Teja Singamsetty commented on PHOENIX-3069:
--------------------------------------------------------------
This is fixed as part of PHOENIX-3113
> Test-only async index builder should not requires tests to run in own mini
> cluster
> ----------------------------------------------------------------------------------
>
> Key: PHOENIX-3069
> URL: https://issues.apache.org/jira/browse/PHOENIX-3069
> Project: Phoenix
> Issue Type: Test
> Reporter: James Taylor
> Assignee: Loknath Priyatham Teja Singamsetty
>
> It appears that the test-only async index builder requires that a new mini
> cluster be spun up to function correctly. Spinning up a separate mini cluster
> is expensive and should be avoided.
> Related to this, AsyncIndexIT is derived directly from BaseTest which is a
> no-no and is dropping it's own tables (which the test framework handles). We
> should be able to test this through a class derived from
> BaseHBaseManagedTimeTableReuseIT which is what we're moving toward. If there
> are a subset of the tests that do require there own cluster, that's ok, but
> let's document why and minimize these.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
