You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jiayi Liao (JIRA)" <ji...@apache.org> on 2018/10/17 13:27:00 UTC

[jira] [Updated] (FLINK-10578) Support writable state queryable state

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

Jiayi Liao updated FLINK-10578:
-------------------------------
    Summary: Support writable state  queryable state  (was: Support writable state in QueryableStateClient)

> Support writable state  queryable state
> ---------------------------------------
>
>                 Key: FLINK-10578
>                 URL: https://issues.apache.org/jira/browse/FLINK-10578
>             Project: Flink
>          Issue Type: New Feature
>          Components: Queryable State, State Backends, Checkpointing
>            Reporter: Jiayi Liao
>            Assignee: Jiayi Liao
>            Priority: Major
>
> I can see that now we support queryable state, why don't we also support the writable state? I've already done this on our own business to initialize the state in window during the program's first run. I think other companies may have other needs to modify the state from outside the job.
> The synchronization is a problem but from my perspective, very few objects will be affected because we can directly operate on the stateTable(for the FsStateBackend), and about the performance, I think it'll be okay if users know about it.
> I'm not very aware of what will be affected except what I said above, please let me know more if anyone has doubt about this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)