[
https://issues.apache.org/jira/browse/IGNITE-24477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-24477:
--------------------------------------
Description:
Currently public script execution uses ForkJoinPool for async execution.
{code:java}
if (cursor.hasNextResult()) {
cursor.nextResult().whenCompleteAsync(this::processCursor);
return;
}
{code}
For example, thin client accepts user specified executor for... something (see
IgniteClient.Builder.asyncContinuationExecutor(...)).
It might be worth somehow adding the ability to define a pool for asynchronous
processing in the embedded client.
was:
Currently public script execution uses ForkJoinPool for async execution.
{code:java}
if (cursor.hasNextResult()) {
cursor.nextResult().whenCompleteAsync(this::processCursor);
return;
}
{code}
For example, thin client accepts user specified executor for... something (see
IgniteClient.Builder.asyncContinuationExecutor(...)).
Perhaps it is worth adding ability to define pool for async processing in the
embedded client.
> Sql. Add ability to define executor that will be used for public script
> execution
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-24477
> URL: https://issues.apache.org/jira/browse/IGNITE-24477
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> Currently public script execution uses ForkJoinPool for async execution.
> {code:java}
> if (cursor.hasNextResult()) {
> cursor.nextResult().whenCompleteAsync(this::processCursor);
> return;
> }
> {code}
> For example, thin client accepts user specified executor for... something
> (see IgniteClient.Builder.asyncContinuationExecutor(...)).
> It might be worth somehow adding the ability to define a pool for
> asynchronous processing in the embedded client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
