Hi, Krzysztof As stated in the description section, this option is used to override the parallelism of a JobVertex, where the key is JobVertex id, you can see [1] for double check. A JobVertex may contain more than one operator, so we cannot override the parallelism of a given operator alone. One possible solution to your problem is to leave Map1 and Map2 unchained and put them into two Vertexes so that they can override their parallelism separately.
[1] https://github.com/apache/flink/blob/b3fb1421fe86129a4e0b10bf3a46704b7132e775/flink-runtime/src/main/java/org/apache/flink/runtime/dispatcher/Dispatcher.java#L1591 Best, Ron Krzysztof Chmielewski <krzysiek.chmielew...@gmail.com> 于2023年8月24日周四 20:08写道： > Hi, > have someone used pipeline.jobvertex-parallelism-overrides [1] property? > > I wonder what actually should be a key here? Operator name? > > What if my operators are chained and I want to override only one of its > elements. For example Source -> (Map1 chained with Map2) -> Sink. Can I > override Map2 only, keeping Map1 as is? If not, what should be used as key > for this chained Map1/Map2 operator then? > > Thanks. > > [1] > https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#pipeline-jobvertex-parallelism-overrides >
