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

Posted to issues@ignite.apache.org by "Maksim Zhuravkov (Jira)" <ji...@apache.org> on 2024/03/27 15:22:00 UTC

[jira] [Assigned] (IGNITE-21852) RecordView. RecordView does not support arbitrary key column order.

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

Maksim Zhuravkov reassigned IGNITE-21852:
-----------------------------------------

    Assignee: Maksim Zhuravkov

> RecordView. RecordView does not support arbitrary key column order.
> -------------------------------------------------------------------
>
>                 Key: IGNITE-21852
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21852
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>            Reporter: Maksim Zhuravkov
>            Assignee: Maksim Zhuravkov
>            Priority: Major
>              Labels: ignite-3
>
> This issue is similar to IGNITE-21797.
> To support reading key part from a record, there should be 
> Issue is caused by the fact that at least a method (for reading Key columns from a full record is missing from a record Marshaller).
> P.S. There is also an issue with MarshallerCache for RecordMarshaller - Since Marshaller cache key for key only part does not include a schema columns (because KvMarshaller manages ordering of columns itself) it could be necessary to update MarshallerCache to always include schema column.



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