[
https://issues.apache.org/jira/browse/FLINK-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15904844#comment-15904844
]
ASF GitHub Bot commented on FLINK-5991:
---------------------------------------
GitHub user tzulitai opened a pull request:
https://github.com/apache/flink/pull/3508
[FLINK-5991] [state-backend, streaming] Expose Broadcast Operator State
This PR exposes broadcast operator state through the `CheckpointedFunction`
interface, by adding broadcast state access methods to `OperatorStateStore`.
Since the functionality was already internally available and had test
workarounds using casting, this PR simply removes those casts and properly
tests the functionality through the `OperatorStateStore` interface.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tzulitai/flink FLINK-5991
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3508.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3508
----
commit 84e02d31f3e77af679728f544629becf2a857be9
Author: Tzu-Li (Gordon) Tai <[email protected]>
Date: 2017-03-10T09:22:22Z
[FLINK-5991] [state-backend, streaming] Expose Broadcast Operator State
This commit exposes broadcast operator state through the
`CheckpointedFunction` interface, by adding broadcast state access
methods to `OperatorStateStore`.
----
> Expose Broadcast Operator State through public APIs
> ---------------------------------------------------
>
> Key: FLINK-5991
> URL: https://issues.apache.org/jira/browse/FLINK-5991
> Project: Flink
> Issue Type: New Feature
> Components: State Backends, Checkpointing, Streaming
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Tzu-Li (Gordon) Tai
> Fix For: 1.3.0
>
>
> The broadcast operator state functionality was added in FLINK-5265, it just
> hasn't been exposed through any public APIs yet.
> Currently, we have 2 streaming connector features for 1.3 that are pending on
> broadcast state: rescalable Kinesis / Kafka consumers with shard / partition
> discovery (FLINK-4821 & FLINK-4022). We should consider exposing broadcast
> state for the 1.3 release also.
> This JIRA also serves the purpose to discuss how we want to expose it.
> To initiate the discussion, I propose:
> 1. For the more powerful {{CheckpointedFunction}}, add the following to the
> {{OperatorStateStore}} interface:
> {code}
> <S> ListState<S> getBroadcastOperatorState(ListStateDescriptor<S>
> stateDescriptor);
> <T extends Serializable> ListState<T>
> getBroadcastSerializableListState(String stateName);
> {code}
> 2. For a simpler {{ListCheckpointed}} variant, we probably should have a
> separate {{BroadcastListCheckpointed}} interface.
> Extending {{ListCheckpointed}} to let the user define either the list state
> type of either {{PARTITIONABLE}} or {{BROADCAST}} might also be possible, if
> we can rely on a contract that the value doesn't change. Or we expose a
> defining method (e.g. {{getListStateType()}}) that is called only once in the
> operator. This would break user code, but can be considered because it is
> marked as {{PublicEvolving}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
