Uploaded image for project: 'Crunch'
  1. Crunch
  2. CRUNCH-551

Make the use of Configuration objects inside of CrunchRecordReader/CrunchInputSplit consistent

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.12.0
    • Fix Version/s: 0.13.0
    • Component/s: Core
    • Labels:
      None

      Description

      Ran into an issue when testing a Crunch-on-Spark pipeline that was caused by an inconsistency in the way we handle Configuration objects inside of CrunchInputSplit and CrunchRecordReader. Basically, we can have different Configuration objects in play at different parts of the InputFormat/InputSplit initialization process depending on when/how the split is deserialized and initialized.

        Attachments

        1. CRUNCH-551.patch
          3 kB
          Josh Wills

          Activity

            People

            • Assignee:
              jwills Josh Wills
              Reporter:
              jwills Josh Wills
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: