Today, if the location constraints are set by the
contributeSchedulingConstraints call, the one-to-one connected downstream
operator won't get those constraints, but they should be configured to have the
same constraints as their one-to-one connected parent operator(s).
So we should propagate location constraints automatically until the constraint
boundary, e.g., a repartitioning connector.
Original issue reported on code.google.com by buyingyi@gmail.com on 24 Apr 2012 at 11:13
Original issue reported on code.google.com by
buyingyi@gmail.com
on 24 Apr 2012 at 11:13