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

Flink Jira Bot updated FLINK-5719:
----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: 
auto-deprioritized-major)

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.


> Let LatencyMarkers completely bypass operators / chains
> -------------------------------------------------------
>
>                 Key: FLINK-5719
>                 URL: https://issues.apache.org/jira/browse/FLINK-5719
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>            Reporter: Tzu-Li (Gordon) Tai
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> Currently, {{LatencyMarker}} s are forwarded through operators via the 
> operator interfaces and methods, i.e. 
> {{AbstractStreamOperator#processLatencyMarker()}},  
> {{Output#emitLatencyMarker()}}, 
> {{OneInputStreamOperator#processLatencyMarker()}} etc.
> The main issue with this is that {{LatencyMarker}} s are essentially internal 
> elements, and the implementation on how to handle them should be final. 
> Exposing them through operator interfaces will allow the user to override the 
> implementation, and also makes the user interface for operators 
> over-complicated.
> [~aljoscha] suggested to bypass such internal stream elements from the 
> operator to keep the operator interfaces minimal, in FLINK-5017.
> We propose a similar approach here for {{LatencyMarker}} as well. Since the 
> chaining output calls contribute very little to the measured latency and can 
> be ignored, instead of passing it through operator chains, latency markers 
> can simply be passed downstream once tasks receive them.



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

Reply via email to