[
https://issues.apache.org/jira/browse/FLINK-16876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073053#comment-17073053
]
Yun Tang commented on FLINK-16876:
----------------------------------
[~azagrebin] If we have not reached an agreement for how we implement event
time TTL especially whether we need to support different state for different
TTL time providers in FLINK-12005. I agree to not introduce configurable
TTLTimeProvider currently as event time TTL is not in road map of flink-1.11.
The rest part is how we use different TTL time provider in unit test. Apart
from implement a customized {{StreamTaskStateInitializer}}, we could also
define a customized state backend to create keyed state backend with mock TTL
time provider. Although these two options are a bit complicated when we
implement unit tests, I think would add a TODO to refactor that part in the
future once more features of TTL is supported. CC [~lsy] [~jark]
> 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)
