[jira] [Updated] (IGNITE-21684) Sql. Exception from a scan operation is not correctly propagated if OrderedPublisher is used.

["Maksim Zhuravkov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-21684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maksim Zhuravkov updated IGNITE-21684:
--------------------------------------
    Labels: ignite-3  (was: )

> Sql. Exception from a scan operation is not correctly propagated if OrderedPublisher is used.
> ---------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-21684
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21684
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Maksim Zhuravkov
>            Priority: Minor
>              Labels: ignite-3
>
> Root cause of exception thrown from an index scan operation  is lost, when OrderedPublisher is being used.
> Reproducer can be found in ItSchemaSyncSingleNodeTest::readWriteOperationAfterDroppingTargetTableIsRejected (change an index to a sorted one).
> {code:java}
>  java.lang.AssertionError: 
>  Expected: a string containing "Table was dropped [table=6]"
>  but: was null
>  Expected :a string containing "Table was dropped [table=6]"
>  Actual   :null
> {code}
> Although a stack trace on a server includes that error:
> {code:java}
> Suppressed: java.util.concurrent.CompletionException: org.apache.ignite.internal.table.distributed.replicator.IncompatibleSchemaException: IGN-TX-12 TraceId:68590499-47c7-46a9-bd5a-d75f2090aebc Table was dropped [table=6]
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)