Major 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.