[jira] [Resolved] (BATCHEE-3) Job/StepContext getExecutionId()/getInstanceId() return wrong value on partition threads

["Romain Manni-Bucau (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BATCHEE-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Romain Manni-Bucau resolved BATCHEE-3.
--------------------------------------

    Resolution: Fixed

> Job/StepContext getExecutionId()/getInstanceId() return wrong value on partition threads
> ----------------------------------------------------------------------------------------
>
>                 Key: BATCHEE-3
>                 URL: https://issues.apache.org/jira/browse/BATCHEE-3
>             Project: BatchEE
>          Issue Type: Bug
>            Reporter: Scott Kurz
>            Assignee: Romain Manni-Bucau
>            Priority: Minor
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)