You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2020/08/31 05:09:45 UTC
[GitHub] [flink-statefun] tzulitai opened a new pull request #135: [FLINK-19095] [remote] Allow state expiration mode for remote function state
tzulitai opened a new pull request #135:
URL: https://github.com/apache/flink-statefun/pull/135
Before this PR, since state was multiplexed, we didn't allow state to have individual state expiration modes, and everything was defaulted to expire with "after-read-and-write" mode.
Now with state de-multiplexed, it is possible to allow this, with the following configuration:
```
functions:
function:
spec:
states:
- name: xxxx
expireAfter: 60000millisecond
expireMode: [after-invoke | after-write]
```
Note that I named the usual `after-read-or-write` module as `after-invoke` in the remote function case.
This is due to the fact that they are semantically equivalent in the remote function case, and naming it as such seems to be less confusing for users using remote functions.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink-statefun] tzulitai closed pull request #135: [FLINK-19095] [remote] Allow state expiration mode for remote function state
Posted by GitBox <gi...@apache.org>.
tzulitai closed pull request #135:
URL: https://github.com/apache/flink-statefun/pull/135
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org