Uploaded image for project: 'Pig'
  1. Pig
  2. PIG-2995

Refactor unit test temporary file allocation patterns to use FileLocalizer.getTemporaryPath

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 0.10.0
    • Fix Version/s: None
    • Component/s: build
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jgordon John Gordon
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: