Hi guys,
Purshatom, I see you checked oozie-1807 into the trunk. So, I have a question, why does it need to throw an exception when someone wants to change a bundle job where one of its coord job is in KILLED state? Due to the change in BundleJobChangeXCommand, this is throwing exceptions when trying to change a RUNNING bundle job where some of the coord jobs are intentionally killed by the user. Thanks, Bowen
