fsk119 commented on code in PR #26630:
URL: https://github.com/apache/flink/pull/26630#discussion_r2127834307
##########
flink-table/flink-table-api-java/src/main/java/org/apache/flink/table/api/config/ExecutionConfigOptions.java:
##########
@@ -443,6 +443,36 @@ public class ExecutionConfigOptions {
"The max number of async retry attempts to make
before task "
+ "execution is failed.");
+ // ------------------------------------------------------------------------
+ // Async ML_PREDICT Options
+ // ------------------------------------------------------------------------
+
+ @Documentation.TableOption(execMode =
Documentation.ExecMode.BATCH_STREAMING)
+ public static final ConfigOption<Integer>
TABLE_EXEC_ASYNC_ML_PREDICT_BUFFER_CAPACITY =
+ key("table.exec.async-ml-predict.buffer-capacity")
+ .intType()
+ .defaultValue(100)
+ .withDescription(
+ "The max number of async i/o operation that the
async ml predict can trigger.");
Review Comment:
If the buffer is full, all messages from the upstream operator will be
subject to backpressure. Flink has a detailed doc about the async io. Hope this
can solve your questions[1]. I don't suggest users to adjust this value,
recently, we are prepare a new FLIP about the rate-limit, which is much
user-friendly.
[1]https://nightlies.apache.org/flink/flink-docs-master/docs/dev/datastream/operators/asyncio/
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
