flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From StefanRRichter <...@git.apache.org>
Subject [GitHub] flink issue #3508: [FLINK-5991] [state-backend, streaming] Expose Broadcast ...
Date Fri, 17 Mar 2017 11:05:26 GMT
Github user StefanRRichter commented on the issue:

    https://github.com/apache/flink/pull/3508
  
    I wonder if there could also exist a case for broadcasting operator state (non-keyed),
where only one operator instance is selected as sender and all others receive on restore.
Furthermore, the union aspect may (or may not) happen at restore time, but not at the time
that a user requests this state. For what this currently does, I think `ReplicatingState`
describes it pretty well. Broadcast would be a good description from the operator's perspective:
it broadcasts the generated data to all peers on restore.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message