falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Isaychuk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-587) Don't delete input data in @AfterClass in falcon-regression tests
Date Thu, 14 Aug 2014 11:00:13 GMT

    [ https://issues.apache.org/jira/browse/FALCON-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096844#comment-14096844

Paul Isaychuk commented on FALCON-587:

As for me we can also use another approach. We can add a *property* into Merlin.properties
where we *list all desirable classes* where data should remain. For other classes data will
be removed by default. 
For example: {quote} retain.data.for=Class1,Class2 {quote} --> We can read this value in
MerlinConstans class. Then we use it in @BeforeClass of each test class. If the name of current
test class is contained in that string then we set parent BaseTestClass boolean flag to false
e.g. {quote} removeData=false; {quote} --> and then we remove (or leave) data after test
ran in @AfterClass of BaseTestClass base on boolean flag.
Makes sense?

> Don't delete input data in @AfterClass in falcon-regression tests
> -----------------------------------------------------------------
>                 Key: FALCON-587
>                 URL: https://issues.apache.org/jira/browse/FALCON-587
>             Project: Falcon
>          Issue Type: Bug
>          Components: merlin
>            Reporter: Ruslan Ostafiychuk
>            Priority: Minor
>         Attachments: FALCON-587.patch
> We can leave input data after tests for debug. Input data will be deleted if we run tests
again in @BeforeMethod (during HadoopUtil.flattenAndPutDataInFolder()).

This message was sent by Atlassian JIRA

View raw message