[
https://issues.apache.org/jira/browse/IGNITE-21684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov resolved IGNITE-21684.
---------------------------------------
Resolution: Fixed
Was fixed in IGNITE-20126
> 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
> Assignee: Konstantin Orlov
> Priority: Minor
> Labels: ignite-3
>
> The root cause of an exception thrown from an sorted index scan operation is
> lost.
> Reproducer can be found in
> ItSchemaSyncSingleNodeTest::readWriteOperationAfterDroppingTargetTableIsRejected
> (change a primary key index to a sorted one get such error).
> {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)
