You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2023/10/13 06:50:00 UTC

[jira] [Assigned] (IGNITE-20576) Rework ClientTableTest# testGetReturningTupleWithUnknownSchemaRequestsNewSchema()

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

Pavel Tupitsyn reassigned IGNITE-20576:
---------------------------------------

    Assignee: Pavel Tupitsyn

> Rework ClientTableTest# testGetReturningTupleWithUnknownSchemaRequestsNewSchema()
> ---------------------------------------------------------------------------------
>
>                 Key: IGNITE-20576
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20576
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Roman Puchkovskiy
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> ClientTableTest#testGetReturningTupleWithUnknownSchemaRequestsNewSchema() makes latest schema version known to the server 2, then it lowers it to 1, so the latest schema version number loses its monotonicity. This monotonicity is now relied upon by the server, so the test should probably be modified to do its job without breaking this invariant.



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