[ 
https://issues.apache.org/jira/browse/FLINK-13062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-13062:
-----------------------------------
    Labels: auto-deprioritized-major pull-request-available stale-minor  (was: 
auto-deprioritized-major pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Set ScheduleMode based on boundedness of streaming Pipeline
> -----------------------------------------------------------
>
>                 Key: FLINK-13062
>                 URL: https://issues.apache.org/jira/browse/FLINK-13062
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>            Reporter: Aljoscha Krettek
>            Priority: Minor
>              Labels: auto-deprioritized-major, pull-request-available, 
> stale-minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The new Blink-based Table Runner needs "streaming pipelines" to be executed 
> with {{ScheduleMode.LAZY_FROM_SOURCES}} if all sources are bounded. The 
> current Blink code base uses a global flag for this and configures the 
> {{StreamGraphGenerator}} accordingly.
> We propose to add an {{isBounded()}} property to {{Transformation}} (formerly 
> known as {{StreamTransformation}}). The property would only be explicitly 
> settable on sources, other transformations inherit the property from their 
> inputs. The {{StreamGraphGenerator}} must use 
> {{ScheduleMode.LAZY_FROM_SOURCES}} if all sources are bounded, otherwise, it 
> should use {{ScheduleMode.EAGER}}, as is the currently existing behaviour.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to