flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stavros Kontopoulos (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (FLINK-7771) Make the operator state queryable
Date Thu, 12 Oct 2017 22:45:01 GMT

    [ https://issues.apache.org/jira/browse/FLINK-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202692#comment-16202692
] 

Stavros Kontopoulos edited comment on FLINK-7771 at 10/12/17 10:44 PM:
-----------------------------------------------------------------------

[~kkl0u] We could overcome some problems by allowing Flink to inform an external system about
state changes. If re-assignment is done the client who issues the queries should know. It
could subscribe to that event channel (the client could push changes to a distributed log
for recovery) in order to correlate state with (operator_id, task_id) and time. This way any
query about state could always point to the correct task. Is this feasible or adds too much
overhead?


was (Author: skonto):
We could overcome some problems by allowing Flink to inform an external system about state
changes. If re-assignment is done the client who issues the queries should know. It could
subscribe to that event channel (the client could push changes to a distributed log for recovery)
in order to correlate state with (operator_id, task_id) and time. This way any query about
state could always point to the correct task. Is this feasible or adds too much overhead?

> Make the operator state queryable
> ---------------------------------
>
>                 Key: FLINK-7771
>                 URL: https://issues.apache.org/jira/browse/FLINK-7771
>             Project: Flink
>          Issue Type: Improvement
>          Components: Queryable State
>    Affects Versions: 1.4.0
>            Reporter: Kostas Kloudas
>            Assignee: Kostas Kloudas
>
> There seem to be some requests for making the operator (non-keyed) state queryable. This
means that the user will specify the *uuid* of the operator and the *taskId*, and he will
be able to access the state that corresponds to that operator and for that specific task.
> This issue will serve to document the discussion on the topic, so that everybody can
participate.
> I also link [~till.rohrmann] and [~skonto] as he also mentioned that this feature could
be helpful.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message