Tzu-Li (Gordon) Tai created FLINK-21678:
-------------------------------------------
Summary: Rename Expiration.expiresAfterReadOrWrite to
Expiration.expiresAfterCall in StateFun
Key: FLINK-21678
URL: https://issues.apache.org/jira/browse/FLINK-21678
Project: Flink
Issue Type: Improvement
Components: Stateful Functions
Reporter: Tzu-Li (Gordon) Tai
Assignee: Tzu-Li (Gordon) Tai
Fix For: statefun-3.0.0
For remote functions in StateFun, a managed remote state with Flink expiration
settings {{expireAfterReadAndWrite}} actually means that a value's TTL timer
will always be refreshed when attempting to invoke the function. This is
because invoking a remote function always entails reading the state from the
state backends (as defined by the request reply protocol).
To avoid any confusion for users, we've decided to rename this expiration
configuration as {{expireAfterCall}} for remote functions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
