[
https://issues.apache.org/jira/browse/FLINK-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-3514:
----------------------------------
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.
> 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: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> 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.20.1#820001)
