[GitHub] apex-core pull request #362: APEXCORE-494 Fixed the dynamic partition issue ...

[chaithu14 <gi...@git.apache.org>]

Github user chaithu14 commented on a diff in the pull request:

    https://github.com/apache/apex-core/pull/362#discussion_r72926469
  
    --- Diff: engine/src/main/java/com/datatorrent/stram/plan/physical/PhysicalPlan.java ---
    @@ -962,8 +963,11 @@ private void redoPartitions(PMapping currentMapping, String note)
           mainPC.operatorIdToPartition.put(p.getId(), newPartition);
         }
     
    +    // Get the deepest down stream mapping
    +    PMapping downStreamMapping = currentMapping;
    --- End diff --
    
    If partitionContexts linked hashmap exists then downStreamMapping be the last element of hasmap otherwise downStreamMapping be the currentMapping.
    Lets say, the physical dag before repartition as below :
    A1 -> B1 -> C1 -> D1 and parallel partition between A -> B and B -> C.
    
    If A is repartitioned to 3 then 
    downStreamMapping would be the Operator C's mapping.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---