[
https://issues.apache.org/jira/browse/FLINK-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210628#comment-15210628
]
ASF GitHub Bot commented on FLINK-3659:
---------------------------------------
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/1831#issuecomment-200945681
I like @aljoscha's idea to separate more explicitly the user state access
and it's implementation. Having an accessor would also allow us to get rid of
the swapping of the actual state objects which are wrapped by the `State`
objects. Then the implementation of a `StateBackend` wouldn't have to be spread
out over the `KvState` classes anymore. This again would make it easier to
integrate the notion of virtual state partitions/shards into `StateBackends`.
So in general, I think it would simplify our current `StateBackend`
implementations noticeable.
> Allow ConnectedStreams to Be Keyed on Only One Side
> ---------------------------------------------------
>
> Key: FLINK-3659
> URL: https://issues.apache.org/jira/browse/FLINK-3659
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Affects Versions: 1.0.0
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
>
> Currently, we only allow partitioned state when both inputs are keyed (with
> the same key type). I think a valid use case is to have only one side keyed
> and have the other side broadcast to publish some updates that are relevant
> for all keys.
> When relaxing the requirement to have only one side keyed we must still
> ensure that the same key is used if both sides are keyed.
> [~gyfora] Did you try this with what you're working on?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
