[
https://issues.apache.org/jira/browse/FLINK-16876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071561#comment-17071561
]
Andrey Zagrebin commented on FLINK-16876:
-----------------------------------------
[~yunta] thanks for looking into this
Can you give more details about what you want to change and where to make it
configurable?
What kind of UT tests are hard to write currently?
Just to notice, the TtlTimeProvider does not depend on backend in general, so
technically it can be configured outside of any backend scope and runtime just
gives it to the backend.
> 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
> Fix For: 1.11.0
>
>
> 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)
