You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/07/13 09:40:20 UTC
[jira] [Created] (PHOENIX-3069) Test-only async index builder
should not requires tests to run in own mini cluster
James Taylor created PHOENIX-3069:
-------------------------------------
Summary: 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)