[
https://issues.apache.org/jira/browse/FLINK-16876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073718#comment-17073718
]
Andrey Zagrebin commented on FLINK-16876:
-----------------------------------------
If we want to test with real backends, I think changing the hardcoded
TtlTimeProvider.DEFAULT to {{ProcessingTimeService#getCurrentProcessingTime}}
is probably the simplest solution for now. It is some coupling and we might
want to refactor it in future. Otherwise, we have to override how we create
backend in StreamTaskStateInitializerImpl or create some custom versions of
backends/wrappers with custom TtlTimeProvider.
> 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)
