[
https://issues.apache.org/jira/browse/FLINK-22300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17450921#comment-17450921
]
Arvid Heise commented on FLINK-22300:
-------------------------------------
Okay I see, so Flink would never evict the data. That is indeed a bug.
What do you think is the proper fix? I have a hard time to come up with proper
semantics beyond saying that users can't use {{TimeEvictor}} with processing
time. For a window in processing time, a user probably wants to retain all
elements before trigger and evict all elements after the trigger in all cases.
For other cases, they would use ingestion or event time.
> Why TimeEvictor of Keyed Windows evictor do not support ProcessingTime of
> TimeCharacteristic
> --------------------------------------------------------------------------------------------
>
> Key: FLINK-22300
> URL: https://issues.apache.org/jira/browse/FLINK-22300
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Affects Versions: 1.11.3
> Reporter: Bo Huang
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> StreamExecutionEnvironment.setStreamTimeCharacteristic(TimeCharacteristic.ProcessingTime).
> The data after Windows process can not be evicted by TimeEvictor of Keyed
> Windows Beause TimestampedValue have no timestamp value.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
