Bug 4787 - SPEC - Sync up Partition Plan JSL and Java Object
SPEC - Sync up Partition Plan JSL and Java Object
Status: RESOLVED WORKSFORME
Product: jbatch
Classification: Unclassified
Component: source
1
All All
: P5 normal
: ---
Assigned To: cvignola
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-12 16:55 UTC by kmukher
Modified: 2013-03-12 19:00 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kmukher 2013-03-12 16:55:30 UTC
The interface for PartitionPlan now has a partitionsOverride parameter. I believe the JSL should reflect this parameter as an optional partitionsOverride attribute on plan. Since property substitution is allowed on any parameter we should know how to handle a change on restart in the number of partitions for a static plan, and ideally it should have the same behavior as the dynamic mapper.

Also, I believe the default value(in the runtime) for this attribute should be false, so the batch container keeps the same number of partitions on a restart and remembers previous partition results unless the JSL explicitly directs the container not to.

<plan partitions="{number}" threads="{number}" partitionsOverride="true|false"/>
Comment 1 cvignola 2013-03-12 17:49:15 UTC
Actually, leaving it off was deliberate.  I consider it an advanced option and an application has to be specifically designed to take advantage of it. So I think it does not belong in the JSL.
Comment 2 kmukher 2013-03-12 19:00:09 UTC
I see, so in the case of a static plan the number of partitions will always remain the same after the first execution, even if a substitution property changes the partitions attribute on restart.