[jira] [Created] (FLINK-16782) Avoid unnecessary check on expired time state when we set visibility as ReturnExpiredIfNotCleanedUp

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (FLINK-16782) Avoid unnecessary check on expired time state when we set visibility as ReturnExpiredIfNotCleanedUp

Shang Yuanchun (Jira)
Yun Tang created FLINK-16782:
--------------------------------

             Summary: Avoid unnecessary check on expired time state when we set visibility as ReturnExpiredIfNotCleanedUp
                 Key: FLINK-16782
                 URL: https://issues.apache.org/jira/browse/FLINK-16782
             Project: Flink
          Issue Type: Improvement
          Components: Runtime / State Backends
    Affects Versions: 1.10.0
            Reporter: Yun Tang
             Fix For: 1.11.0


Current implementation of getting unexpired value would always check whether this ttl value is expired first:
{code:java}
// code placeholder
<V> V getUnexpired(TtlValue<V> ttlValue) {
        return ttlValue == null || (expired(ttlValue) && !returnExpired) ? null : ttlValue.getUserValue();
}
{code}
However, this check could be avoided if we set return expired time, we could improve the performance by check whether to \{{returnExpired}} first.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)