Bug 4525 - JobInstance completion clarification
JobInstance completion clarification
Status: RESOLVED FIXED
Product: jbatch
Classification: Unclassified
Component: source
1
All All
: P5 minor
: ---
Assigned To: cvignola
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-17 15:18 UTC by mminella
Modified: 2013-01-24 19:24 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mminella 2013-01-17 15:18:26 UTC
The section 4.1.3 (page 12), is a bit confusing and vague.  A JobInstance is not considered complete unless ONE execution completes successfully.  That paragraph feels like it dances around that fact without just coming out and saying it.  It states that a JobExecution cannot be restarted but then again, a JobExecution isn't restarted (A new JobExecution is created on a restart of a JobInstance).  The point about a JobInstance being complete may really belong in section 4.1.1.
Comment 1 cvignola 2013-01-23 22:26:01 UTC
I found of those details to be unnecessary in this section and removed them.  I considered adding some to the JobInstance explanation (4.1.1) but felt it unnecessary.  

Section 4.1.3 JobExecution was revised to say simply:

A JobExecution refers to the technical concept of a single attempt to run a Job. Each time is job is started or restarted, a new JobExecution is created,  belonging to the same JobInstance.
Comment 2 waynexlund 2013-01-24 05:19:55 UTC
I like it but there's a typo - "Each time is job is started or restarted" should be "Each time a job ..."
Comment 3 cvignola 2013-01-24 19:24:42 UTC
(In reply to comment #2)

Think I was staring too long at the document yesterday :)   Thanks, Wayne.  I corrected it in v1.2, which I'm posting this week.

> I like it but there's a typo - "Each time is job is started or restarted"
> should be "Each time a job ..."