[ 
https://issues.apache.org/jira/browse/FLINK-18467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Zagrebin updated FLINK-18467:
------------------------------------
    Description: 
changing whether the state has TTL or not is not easy as it requires migration
but changing how to treat the expiration timestamp is possible, e.g. value of 
TTL or when to update/remove it
this applies only to changes between job restarts but not while the job is 
running at the moment

  was:
changing whether the state has TTL or not is not easy as it requires migration
but changing how to treat the expiration timestamp is possible, e.g. value of 
TTL or when to update/remove it


> Document what can be reconfigured for state with TTL between job restarts
> -------------------------------------------------------------------------
>
>                 Key: FLINK-18467
>                 URL: https://issues.apache.org/jira/browse/FLINK-18467
>             Project: Flink
>          Issue Type: Task
>          Components: Runtime / State Backends
>    Affects Versions: 1.8.4
>            Reporter: Andrey Zagrebin
>            Priority: Major
>
> changing whether the state has TTL or not is not easy as it requires migration
> but changing how to treat the expiration timestamp is possible, e.g. value of 
> TTL or when to update/remove it
> this applies only to changes between job restarts but not while the job is 
> running at the moment



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

Reply via email to