Pig
  1. Pig
  2. PIG-2578

Multiple Store-commands mess up mapred.output.dir.

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.8.1, 0.9.2
    • Fix Version/s: 0.10.0, 0.11
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      When one runs a pig-script with multiple storers, one sees the following:
      1. When run as a script, Pig launches a single job.
      2. PigOutputCommitter::setupJob() calls the underlyingOutputCommitter::setupJob(), once for each storer. But the mapred.output.dir is the same for both calls, even though the storers write to different locations.

      This was originally seen in HCATALOG-276, when HCatalog's end-to-end tests are run against Pig.
      (https://issues.apache.org/jira/browse/HCATALOG-276)

      Sample pig-script (near identical to HCatalog's Pig_Checkin_4 test):

      a = load 'keyvals' using org.apache.hcatalog.pig.HCatLoader();
      split a into b if key<200, c if key >=200;
      store b into 'keyvals_lt200' using org.apache.hcatalog.pig.HCatStorer();
      store c into 'keyvals_ge200' using org.apache.hcatalog.pig.HCatStorer();

      I've suggested a workaround in HCat for the time being, but I think this might be something that needs fixing in Pig.

      Thanks.

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Daniel Dai
              Reporter:
              Mithun Radhakrishnan
            • Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development