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 Pereslegin (Jira)" <ji...@apache.org> on 2023/02/02 09:23:00 UTC

[jira] [Updated] (IGNITE-18699) Sql. Simplify colocation group implementation to better fit current project concepts

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

Pavel Pereslegin updated IGNITE-18699:
--------------------------------------
    Description: 
Currently {{ColocationGroup}} stores "assigments" in a "2-dimensional" list (List of Lists).
Each element of which corresponds the partition number and stores nodes list (assignment).
The first node in this list is the primary node (replica) for the partition.

But production code only works with the primary replica, so it seems that we can simplify the implementation and replace the "2 dimensional" list with a simple list with primary replicas.

  was:
Currently {{ColocationGroup}} stores "assigments" in a "2-dimensional" list (List of Lists).
Each element of which corresponds the partition number and stores nodes list (assignment).
The first node in this list is the primary node (replica) for the partition.

Sql engine only works with the primary replica, so it seems that we can simplify the implementation and replace the "2 dimensional" list with a simple list with primary replicas.


> Sql. Simplify colocation group implementation to better fit current project concepts
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-18699
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18699
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>
> Currently {{ColocationGroup}} stores "assigments" in a "2-dimensional" list (List of Lists).
> Each element of which corresponds the partition number and stores nodes list (assignment).
> The first node in this list is the primary node (replica) for the partition.
> But production code only works with the primary replica, so it seems that we can simplify the implementation and replace the "2 dimensional" list with a simple list with primary replicas.



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