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

Posted to issues@ignite.apache.org by "Andrey Khitrin (Jira)" <ji...@apache.org> on 2025/07/03 11:18:00 UTC

[jira] [Created] (IGNITE-25826) Incompatible changes in RecoveryApi after enabling collocation

Andrey Khitrin created IGNITE-25826:
---------------------------------------

             Summary: Incompatible changes in RecoveryApi after enabling collocation
                 Key: IGNITE-25826
                 URL: https://issues.apache.org/jira/browse/IGNITE-25826
             Project: Ignite
          Issue Type: Bug
          Components: rest ai3
    Affects Versions: 3.1
            Reporter: Andrey Khitrin


In IGNITE-25708, REST API was changed in a non-compatible way: some field in
{color:#000000}LocalPartitionStateResponse, being non-nullable previously,{color} were marked as nullable.
 
After that, in IGNITE-25687, colocation was enabled by default, and this API had started to return actual nulls. This breaks client code that previously used this API to check partitions status.
In order to keep compatibility, either this behavior should be fixed, or an alternative approach must be provided. In some cases, it's important to control an actual amount of replicas created for the given table.



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