[
https://issues.apache.org/jira/browse/IGNITE-22585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860148#comment-17860148
]
Pavel Pereslegin edited comment on IGNITE-22585 at 6/26/24 12:42 PM:
---------------------------------------------------------------------
Currently this issue reproduced locally (on my local machine) using the
following steps:
1. in PrepareServiceImpl.prepareAsync set .plannerTimeout(10)
2. add any check that root is null in ExecutionServiceImpl.executeFragment in
{{if (!(node instanceof Outbox)) {}} branch, for example {{if (root == null)
new NullPointerException().printStackTrace();}} before
{{root.complete(rootNode);}} call.
3. run ItSqlAsynchronousApiTest.testQueryTimeout()
was (Author: xtern):
Currently this issue reproduced locally (on my local machine) using the
following steps:
1. in PrepareServiceImpl.prepareAsync set .plannerTimeout(10)
2. add any check that root is null in ExecutionServiceImpl.executeFragment in
{{if (!(node instanceof Outbox)) {}} branch, for example {{if (root == null)
new NullPointerException().printStackTrace();}}
3. run ItSqlAsynchronousApiTest.testQueryTimeout()
> Sql. ExecutionService timeout at the start of a query. Possible NPE
> -------------------------------------------------------------------
>
> Key: IGNITE-22585
> URL: https://issues.apache.org/jira/browse/IGNITE-22585
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
>
> Query timeouts introduced additional failure conditions in ExecutionService.
> Review code of the DistributedQueryManager to ensure new failure conditions
> are handled properly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
