[
https://issues.apache.org/jira/browse/FLINK-16876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072613#comment-17072613
]
Andrey Zagrebin commented on FLINK-16876:
-----------------------------------------
[~yunta]
I do not think that we have to limit time provider for all TTL states of
operators by the StreamTimeCharacteristic of the whole pipeline. The time
characteristics for the pipeline and for each state TTL can technically differ.
Although, this is something to discuss in FLINK-12005. Therefore, if the
problem is just in unit testing at the moment then I would rather suggest now
to pass ttlTimeProvider to the test harness. The harness could pass it to its
created StreamTaskStateInitializer which would use it for creating the backend.
This would be less invasive at the moment. What do you think?
> 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)
