[jira] [Resolved] (IGNITE-16370) Use precomputed hash of a SearchRow in storage

["Aleksandr Polovtcev (Jira)" <ji...@apache.org>]

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

Aleksandr Polovtcev resolved IGNITE-16370.
------------------------------------------
    Resolution: Won't Fix

Closing this issue as the Partition Storage implementation is deprecated

> Use precomputed hash of a SearchRow in storage 
> -----------------------------------------------
>
>                 Key: IGNITE-16370
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16370
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Aleksandr Polovtcev
>            Assignee: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>
> After IGNITE-16102, Partition Storage based on RocksDB uses {{Arrays.hashCode}} to compute the hash of the storage key. However, binary representation relies on {{BinaryRow}} serialization, which already contains a precomputed hash code. It is proposed to add a {{keyHash}} method to the {{SearchRow}} interface, which will provide the hash code from the underlying {{BinaryRow}} to the storage.



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