[
https://issues.apache.org/jira/browse/FLINK-14950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16984922#comment-16984922
]
Biao Liu commented on FLINK-14950:
----------------------------------
[~wind_ljy],
{quote}By the way, Since the key access is not allowed we have to call
context.toString() and analyze the pattern to get the binding key.
{quote}
Sorry to here that :(
I'm not saying it's a bad idea to make the key accessible in window context.
It's just, you know, I didn't see a strong reason to do so. Your case seems to
be quite complicated. I still have not fully understood your scenario. Even if
you could get the key from context, how do you remove state from all windows
associate with the key? The trigger is for window, not for key.
{quote}Maybe we should wait for more responses from others.
{quote}
Yeh, that would be great if someone else could give us a better idea.
> Support getKey in WindowOperator.Context
> ----------------------------------------
>
> Key: FLINK-14950
> URL: https://issues.apache.org/jira/browse/FLINK-14950
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Affects Versions: 1.9.1
> Reporter: Jiayi Liao
> Priority: Major
>
> In our scenario, user needs to access the key of {{WindowOperator.Context}}
> to determine how to deal with the window.
> I think it's reasonable to support {{getKey()}} method in
> {{WindowOperator.Context}}.
> cc [~aljoscha]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
