[
https://issues.apache.org/jira/browse/FLINK-12229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830143#comment-16830143
]
Till Rohrmann commented on FLINK-12229:
---------------------------------------
My current take would be to only look at the input result partitions instead of
the state of the overall {{IntermediateDataSet}}. This could speed up
deployments. With this in mind, {{ANY}}/{{ALL}} should work also with respect
to the input result partitions.
At the moment, I would suggest to make the {{SchedulingIntermediateDataSet}} an
aspect of the {{LazyFromSourcesSchedulingStrategy}} implementation. If we see
later that more {{SchedulingStrategy}} implementations need this feature, then
we can make it part of the {{SchedulingTopology}}. Would this work?
> Implement Lazy Scheduling Strategy
> ----------------------------------
>
> Key: FLINK-12229
> URL: https://issues.apache.org/jira/browse/FLINK-12229
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Reporter: Gary Yao
> Assignee: BoWang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Implement a {{SchedulingStrategy}} that covers the functionality of
> {{ScheduleMode.LAZY_FROM_SOURCES}}, i.e., vertices are scheduled when all the
> input data are available.
> Acceptance Criteria:
> * New strategy is tested in isolation using test implementations (i.e.,
> without having to submit a job)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
