You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2023/03/28 07:51:00 UTC
[jira] [Resolved] (IGNITE-18974) Sql. Exception silently skipped.
[ https://issues.apache.org/jira/browse/IGNITE-18974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evgeny Stanilovsky resolved IGNITE-18974.
-----------------------------------------
Resolution: Not A Problem
Was fixed in [1]
[1] https://issues.apache.org/jira/browse/IGNITE-18878
> Sql. Exception silently skipped.
> --------------------------------
>
> Key: IGNITE-18974
> URL: https://issues.apache.org/jira/browse/IGNITE-18974
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 3.0.0-beta1
> Reporter: Evgeny Stanilovsky
> Assignee: Evgeny Stanilovsky
> Priority: Major
> Labels: calcite3-required, ignite-3
>
> DistributedQueryManager#acknowledgeFragment silently skip proposed exception.
> Fast reproducer is to hack implementation and write smth like:
> {noformat}
> private void acknowledgeFragment(String nodeName, long fragmentId, @Nullable Throwable ex) {
> Exception ex0 = new ...
> if (ex0 != null) {
> ... and so on
> {noformat}
> The only problem we can observe looks like :
> {noformat}
> at org.apache.ignite.internal.sql.engine.exec.ExecutionServiceImplTest.testCancelOnInitiator(ExecutionServiceImplTest.java:188)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)