[MRUNIT-66] null input checks and behavior on no input to a driver are inconsistent

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.8.1
• Fix Version/s: 0.9.0
• Assignee: Jim Donofrio
• Reporter: Jim Donofrio
• Due: 25/Mar/12
• Created: 26/Feb/12 08:04
• Updated: 23/Oct/12 16:05
• Resolved: 26/Mar/12 01:02

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