[
https://issues.apache.org/jira/browse/FLINK-16876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074439#comment-17074439
]
Andrey Zagrebin commented on FLINK-16876:
-----------------------------------------
`TtlTimeProvider.DEFAULT` was not really planned to stay forever, it may be
removed during the event time implementation if meeded.
Passing a mock TtlTimeProvider to AbstractStreamOperatorTestHarness and
StreamTaskStateInitializerImpl sounds good to me.
Do we need this issue? If not, could you close it? From the first glance, It
sounds a bit like we want to make TtlTimeProvider configurable by users which
can be an option at some point but probably not now.
> 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)
