[
https://issues.apache.org/jira/browse/FLINK-1092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125422#comment-14125422
]
Stephan Ewen commented on FLINK-1092:
-------------------------------------
The rational behind that decision was that, in order to access a partitioned
state, the accessing operator must be partitioned as well.
Making the access via a join (cogroup) assures that and outlined a consistent
way to integrate into the optimizer.
We are bit by bit adding operations with more explicit control, so explicit
access to the state would be a logical step. We need to think about whether to
mark an operator as "state accessing", or whether we should totally leave it to
the user to correctly partition the data (for example like in pull request
https://github.com/apache/incubator-flink/pull/108)
> Allow operations, other than join and cogroup, on the solution set
> ------------------------------------------------------------------
>
> Key: FLINK-1092
> URL: https://issues.apache.org/jira/browse/FLINK-1092
> Project: Flink
> Issue Type: Improvement
> Components: Iterations
> Reporter: Vasia Kalavri
> Priority: Minor
> Labels: feature
>
> Currently, join and cogroup are the only operations allowed on the solution
> set. We should make the solution set usable for any type of operation,
> possibly using special functions.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
