[jira] [Created] (FLINK-20049) Simplify handling of "request split".

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (FLINK-20049) Simplify handling of "request split".

Shang Yuanchun (Jira)
Stephan Ewen created FLINK-20049:
------------------------------------

             Summary: Simplify handling of "request split".
                 Key: FLINK-20049
                 URL: https://issues.apache.org/jira/browse/FLINK-20049
             Project: Flink
          Issue Type: Improvement
          Components: API / Core
            Reporter: Stephan Ewen
            Assignee: Stephan Ewen
             Fix For: 1.12.0


This issue is similar to FLINK-19265

Split assignment events are treated specially by the source API. Users do not create them directly but call methods on the contexts to assign splits.

The {{RequestSplitEvent}} is in contrast to that a custom user event and needs to be handled like a custom event, when sent by enumerators and received by the readers.

That seems a bit confusing and inconsistent, given that {{RequestSplitEvent}} is essential for all use cases with pull-based split assignment, which is pretty much any batch use case and various streaming use cases. The event should be on the same level as the AddSplitEvent.

I suggest that we add a {{SourceReaderContext.requestSplit()}} and {{SplitEnumerator.handleSplitRequest()}}, to have split requests and responses symmetrical.



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