[
https://issues.apache.org/jira/browse/FLINK-19438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265895#comment-17265895
]
Till Rohrmann commented on FLINK-19438:
---------------------------------------
I agree with you that it would be nice to give proper guarantees for accessing
state via queryable state [~sheep]. However, as [~kkl0u] said this feature is
at the moment no longer actively developed. Hence, I will close this issue as
won't do for the time being.
> Queryable State needs to support both read-uncommitted and read-committed
> --------------------------------------------------------------------------
>
> Key: FLINK-19438
> URL: https://issues.apache.org/jira/browse/FLINK-19438
> Project: Flink
> Issue Type: Wish
> Components: Runtime / Queryable State
> Reporter: sheep
> Priority: Major
>
> Flink exposes its managed keyed (partitioned) state to the outside world and
> allows the user to query a job’s state from outside Flink. From a traditional
> database isolation-level viewpoint, the queries access uncommitted state,
> thus following the read-uncommitted isolation level.
> I fully understand Flink provides read-uncommitted state query in order to
> query real-time state. But the read-committed state is also important (I
> cannot fully explain). From Flink 1.9, querying even modifying the state in
> Checkpoint has been implemented. The state in Checkpoint is equivalent to
> read-committed state. So, users can query read-committed state via the state
> processor api.
> *Flink should provide users for configuration of isolation level of
> Queryable State by integration of the two levels of state query.*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
