phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Loknath Priyatham Teja Singamsetty (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-3069) Test-only async index builder should not requires tests to run in own mini cluster
Date Mon, 01 Aug 2016 16:45:20 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Loknath Priyatham Teja Singamsetty  resolved PHOENIX-3069.
----------------------------------------------------------
    Resolution: Fixed

> 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)

Mime
View raw message