Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
Let me first say, I'm not verifying this "bug" report with a testcase. I'm simply assuming it exists since it exists in the original RI 'jbatch' code.
This issue is described here:
https://java.net/bugzilla/show_bug.cgi?id=5164
Not sure how critical this is; the usecase provoking the original report was based on a misunderstanding.
But the root cause stems from the RI's use of an internal-only execution id in internally handling both types of parallel work: splits and partitions. There's no spec justification for surfacing these as first-class execution/instance ids, however.