[ 
https://issues.apache.org/jira/browse/FLINK-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328952#comment-17328952
 ] 

Flink Jira Bot commented on FLINK-3514:
---------------------------------------

This major issue is unassigned and itself and all of its Sub-Tasks have not 
been updated for 30 days. So, it has been labeled "stale-major". If this ticket 
is indeed "major", please either assign yourself or give an update. Afterwards, 
please remove the label. In 7 days the issue will be deprioritized.

> Add support for slowly changing streaming broadcast variables
> -------------------------------------------------------------
>
>                 Key: FLINK-3514
>                 URL: https://issues.apache.org/jira/browse/FLINK-3514
>             Project: Flink
>          Issue Type: New Feature
>          Components: API / DataStream
>            Reporter: Stephan Ewen
>            Priority: Major
>              Labels: stale-major
>
> With "slow changing inputs", I mean auxiliary data sets that change over 
> time. Think about dictionaries, set of rules, etc that are updates at slow 
> rates and then applied onto another stream.
> They are a bit like broadcast variables in the DataSet API, but not constant 
> over the entire lifetime of the job.
> One can currently approximate this via connected streams:
> {code}
> DataStream<Rule> rules = ...
> DataStream<Event> events = ...
> rules.broadcast().connect(events).flatMap(...);
> {code}
> The disadvantage is that one has no control that the broadcasted "rules" 
> input is materialized in the function before the "events" are delivered.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to