You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@pig.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2013/02/11 04:09:12 UTC

[jira] [Assigned] (PIG-2995) Refactor unit test temporary file allocation patterns to use FileLocalizer.getTemporaryPath

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

Jarek Jarcec Cecho reassigned PIG-2995:
---------------------------------------

    Assignee: Jarek Jarcec Cecho
    
> Refactor unit test temporary file allocation patterns to use FileLocalizer.getTemporaryPath
> -------------------------------------------------------------------------------------------
>
>                 Key: PIG-2995
>                 URL: https://issues.apache.org/jira/browse/PIG-2995
>             Project: Pig
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.10.0
>            Reporter: John Gordon
>            Assignee: Jarek Jarcec Cecho
>            Priority: Minor
>
> Pig unit tests have a lot of diverse patterns for temporary file allocation.  Not all of them are best practices.  There is an abstraction that could house best practices for test temporary file allocation -- FileLocalizer.getTemporaryPath.  With this, we should be able to have all/most of the temporary file usage fall under just a few methods that can handle arbitrary pig contexts and provide more flexibility around testing pig with different fs implementations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira