You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Liya Fan (JIRA)" <ji...@apache.org> on 2019/04/08 02:25:00 UTC

[jira] [Commented] (FLINK-4859) Clearly Separate Responsibilities of StreamOperator and StreamTask

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

Liya Fan commented on FLINK-4859:
---------------------------------

Hi [~aljoscha], would you please give more descriptions about this issue?

It seems this issue was opened long ago. Is it still an issue now?

> Clearly Separate Responsibilities of StreamOperator and StreamTask
> ------------------------------------------------------------------
>
>                 Key: FLINK-4859
>                 URL: https://issues.apache.org/jira/browse/FLINK-4859
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>            Reporter: Aljoscha Krettek
>            Priority: Critical
>
> Currently, {{StreamTask}} and {{StreamOperator}} perform a complicated dance for certain operations. For example, when restoring from a snapshot, the state backends are restored in the {{StreamTask}}, but only after {{StreamTask}} calls restore on the operator and the operator asks for the backends. There is no clear separation/modularisation with properly defined interfaces right now.
> The code works right now but maintainability/understandability could be greatly improved.



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