[
https://issues.apache.org/jira/browse/FLINK-16876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073970#comment-17073970
]
Yun Tang commented on FLINK-16876:
----------------------------------
[~azagrebin] I think it's not so good to couple the concept of
{{ProcessingTimeService}} and {{TtlTimeProvider}} directly at this moment which
would also lead TtlTimeProvider.DEFAULT to be totally meaningless.
I have crated a new issue FLINK-16949 focusing on enhance
{{AbstractStreamOperatorTestHarness}} and already prepared a PR locally.
> Make TtlTimeProvider configurable when creating keyed state backend
> -------------------------------------------------------------------
>
> Key: FLINK-16876
> URL: https://issues.apache.org/jira/browse/FLINK-16876
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Affects Versions: 1.10.0
> Reporter: Yun Tang
> Priority: Major
>
> Currently, we would always use TtlTimeProvider.DEFAULT to create keyed state
> backend. This is somehow acceptable since we only support processing time for
> TTL now. However, this would make UT tests which would verify TTL logic not
> so convenient like FLINK-16581.
> I propose to let TtlTimeProvider configurable when creating keyed state
> backend to not block other feature development.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
