tree b607e5dfb210dc63b413d1c03359e84a5e80a01c
parent 5e6e05b74701ec8617af966f3944a56023fd2783
author Tzu-Li (Gordon) Tai <tzulitai@apache.org> 1615259718 +0800
committer Tzu-Li (Gordon) Tai <tzulitai@apache.org> 1615261291 +0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQIzBAABCAAdFiEEHB4jlNMZThlEYTSI8yCYbTXDPWoFAmBG7msACgkQ8yCYbTXD
 PWqOmg//fnHUTCmKNo28C5vwxFaiuo1hSj+SGrWa0ES1OaHgN3rN8PCp6SxQzauE
 M+KGeDHsJ8Cz6v/DmQkNzkNOCtJXRr7gq4PZCwhCJ+ZopgdTzFN/GRJWKcqfI1wN
 /kz+KeZkHaUGHBHeFM3cnS2eheon6fnBJHFOC4cYgpQeVc8mixEiFoudeNlWEj6k
 sOzEiUIiQ0fX5mUtlgV2sNLG3M+jRSuy/ZQa7SAf9nlRgKN0weN6EKsmN+EM17nU
 3/0qcsd57Ig6+IDHHGApyfDM82KcyousXMdLzcp8GtQd9xSXrN9KKqBqyxT9AsMK
 hSF/5r9VisdmWAAya/EyiihbFTr5LmSLT7hHg86Ewxy6fTV2ABGOoltcBEXpv2hf
 Dfcc3+sTC3TLAqYAcev0qVPRC71Ip7+poOwIeyb+hGRG0x96F3M49ODpPPt+5JBd
 SjWejDHYulL9yhfdsG3QJ/2GtNnOy6evlv/TYoME8vlVLd9vgJzVf7ZziXmABVBP
 PQAaHrPVmBNj+k4jHmbr5nWGSiPJXnNKGsiHSCe4AQTEm437ni64quGTG/F4deBn
 3aMwBh/cm5AhVK4ijDkNTu/NPON3NE71eRgWiT5exQS3kZusEJW1kKisFdprX5+h
 1NAlc8kRlxeCrleMyxFysbYLteWB0G3Bt4HkjxmBJQEXD2SHG9s=
 =t+mj
 -----END PGP SIGNATURE-----

[FLINK-21678] Rename expiresAfterReadOrWrite to expiresAfterCall in Java SDK

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.