[
https://issues.apache.org/jira/browse/FLINK-7129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141659#comment-16141659
]
Dawid Wysakowicz edited comment on FLINK-7129 at 8/25/17 2:02 PM:
------------------------------------------------------------------
I meant that if I have some keyed state in operator than I cannot use it in the
method {{processElement2}}. It is not a problem in case of CEP as the second
stream will update only operator state (unionListState).
Have some doubts though about this solution, because it assumes the keySelector
for second stream is used only for accessing proper keyStateBackend.
E.g the non-keyed stream cannot be passed as the first stream because of the
check in {{StreamGraphGenerator#transformTwoInputTransform:589}}. I wonder if
using this trick won't introduce some indirect limitations to lower level parts
of flink.
was (Author: dawidwys):
I meant that if I have some keyed state in operator than I cannot use it in the
method `processElement2`. It is not a problem in case of CEP as the second
stream will update only operator state (unionListState).
Have some doubts though about this solution, because it assumes the keySelector
for second stream is used only for accessing proper keyStateBackend.
E.g the non-keyed stream cannot be passed as the first stream because of the
check in `StreamGraphGenerator#transformTwoInputTransform:589`. I wonder if
using this trick won't introduce some indirect limitations to lower level parts
of flink.
> Dynamically changing patterns
> -----------------------------
>
> Key: FLINK-7129
> URL: https://issues.apache.org/jira/browse/FLINK-7129
> Project: Flink
> Issue Type: New Feature
> Components: CEP
> Reporter: Dawid Wysakowicz
> Assignee: Dawid Wysakowicz
>
> An umbrella task for introducing mechanism for injecting patterns through
> coStream
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
