You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (Jira)" <ji...@apache.org> on 2026/08/04 16:30:00 UTC

[jira] [Created] (IGNITE-28953) Calcite: PlanExecutionTest and ContinuousExecutionTest fail after IGNITE-28937 due to uninitialized message factory

Anton Vinogradov created IGNITE-28953:
-----------------------------------------

             Summary: Calcite: PlanExecutionTest and ContinuousExecutionTest fail after IGNITE-28937 due to uninitialized message factory
                 Key: IGNITE-28953
                 URL: https://issues.apache.org/jira/browse/IGNITE-28953
             Project: Ignite
          Issue Type: Bug
          Components: messaging
            Reporter: Anton Vinogradov
            Assignee: Anton Vinogradov


IGNITE-28937 added an assert to AbstractMarshallableMessageFactoryProvider.loadGenerated(): when a generated companion constructor takes a Marshaller, the provider must be initialized via init() first. In production IgniteKernal#initProvider() always calls init(), so the assert never fires there.

PlanExecutionTest and ContinuousExecutionTest create CalciteMessageFactory without calling init() (they only need direct type registration), so 38 tests fail in the Calcite SQL 2 suite with:

{noformat}java.lang.AssertionError: QueryStartRequestMarshaller takes a marshaller, but none was provided
    at org.apache.ignite.internal.plugin.AbstractMarshallableMessageFactoryProvider.loadGenerated(AbstractMarshallableMessageFactoryProvider.java:118){noformat}

Fix: initialize the factory with jdk marshallers in these tests, the same way core tests do (see CoreMessagesProvider usages with Marshallers.jdk()).



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