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

Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2022/10/27 15:32:00 UTC

[jira] [Resolved] (IGNITE-17205) Need to create primary index implementation

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

Alexander Lapin resolved IGNITE-17205.
--------------------------------------
    Resolution: Won't Fix

Was implemented within https://issues.apache.org/jira/browse/IGNITE-17859

> Need to create primary index implementation
> -------------------------------------------
>
>                 Key: IGNITE-17205
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17205
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Sergey Uttsel
>            Priority: Major
>              Labels: ignite-3
>
> Now VersionedRowStore use a dummy primary index to operate with data in storage.
> Need to create a primary index implementation to replace it.
> By the way we need to think about use cases when we don't have a key and need to do a scan operation, for example sql queries. May be we don't need a primary index in VersionedRowStore.



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