Hi all, I was wondering if the current API for PipelineResult might open the door to inconsistencies stemming from cancel() or waitUntilFinish() returning one state, and getState() returning another? Are such cases legit?
PipelineResult's API has a getState() method: State getState(); at the same time other methods such as cancel() and waitUntilFinish() return State as well: State waitUntilFinish(Duration duration); State cancel() throws IOException; Is this intentional? The alternative would be making cancel() and waitUntilFinish() return void, so that the only (and thus consistent) way to obtain a PipelineResult's state would be via getState(). Am I missing something? Regards, Stas
