You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Burak Yavuz (Jira)" <ji...@apache.org> on 2020/01/29 02:21:00 UTC
[jira] [Created] (SPARK-30669) Introduce AdmissionControl API to
Structured Streaming
Burak Yavuz created SPARK-30669:
-----------------------------------
Summary: Introduce AdmissionControl API to Structured Streaming
Key: SPARK-30669
URL: https://issues.apache.org/jira/browse/SPARK-30669
Project: Spark
Issue Type: Improvement
Components: Structured Streaming
Affects Versions: 2.4.4
Reporter: Burak Yavuz
In Structured Streaming, we have the concept of Triggers. With a trigger like Trigger.Once(), the semantics are to process all the data available to the datasource in a single micro-batch. However, this semantic can be broken when data source options such as `maxOffsetsPerTrigger` (in the Kafka source) rate limit the amount of data read for that micro-batch.
We propose to add a new interface `SupportsAdmissionControl` and `ReadLimit`. A ReadLimit defines how much data should be read in the next micro-batch. `SupportsAdmissionControl` specifies that a source can rate limit its ingest into the system. The source can tell the system what the user specified as a read limit, and the system can enforce this limit within each micro-batch or impose it's own limit if the Trigger is Trigger.Once() for example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org