MRUnit
  1. MRUnit
  2. MRUNIT-66

null input checks and behavior on no input to a driver are inconsistent

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 0.8.1
    • Fix Version/s: 0.9.0
    • Labels:
      None

      Description

      the MapDriver class does not allow null input values if using setInput(Pair) but does allow null input if using setInputKey, setInputValue, or setInput(key, value)

      Also the MapDriver, ReduceDriver classes will throw null pointer exceptions with no input while the MapReduceDriver and Pipeline classes will just log warnings

        Activity

          People

          • Assignee:
            Jim Donofrio
            Reporter:
            Jim Donofrio
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Resolved:

              Development