You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Oleg Novoyavchev (Jira)" <ji...@apache.org> on 2021/09/02 10:53:00 UTC

[jira] [Created] (FLINK-24127) Asynchronous I/O documentation should be updated

Oleg Novoyavchev created FLINK-24127:
----------------------------------------

             Summary: Asynchronous I/O documentation should be updated
                 Key: FLINK-24127
                 URL: https://issues.apache.org/jira/browse/FLINK-24127
             Project: Flink
          Issue Type: Bug
          Components: API / DataStream, Documentation
    Affects Versions: 1.11.0
            Reporter: Oleg Novoyavchev


As the restriction that the AsyncWaitOperator must be at a head of a chain was removed in Flink 1.11, the Acync I/O documentation should the updated in the part of conclusive caveat. The following paragraph perhaps should be removed or actualised:

"*The operator for AsyncFunction (AsyncWaitOperator) must currently be at the head of operator chains for consistency reasons*

For the reasons given in issue {{FLINK-13063}}, we currently must break operator chains for the {{AsyncWaitOperator}} to prevent potential consistency problems. This is a change to the previous behavior that supported chaining. User that require the old behavior and accept potential violations of the consistency guarantees can instantiate and add the {{AsyncWaitOperator}} manually to the job graph and set the chaining strategy back to chaining via {{AsyncWaitOperator#setChainingStrategy(ChainingStrategy.ALWAYS)}}."



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