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

Posted to issues@geode.apache.org by "Nabarun Nag (Jira)" <ji...@apache.org> on 2021/03/23 18:53:00 UTC

[jira] [Resolved] (GEODE-9044) Introduce RedisKey as key object for RedisData entries

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

Nabarun Nag resolved GEODE-9044.
--------------------------------
    Resolution: Fixed

> Introduce RedisKey as key object for RedisData entries
> ------------------------------------------------------
>
>                 Key: GEODE-9044
>                 URL: https://issues.apache.org/jira/browse/GEODE-9044
>             Project: Geode
>          Issue Type: Improvement
>          Components: redis
>            Reporter: Jens Deppe
>            Assignee: Jens Deppe
>            Priority: Major
>              Labels: blocks-1.14.0, pull-request-available
>             Fix For: 1.14.0
>
>
> Currently we are using a {{ByteArrayWrapper}} as the key for all redis entries. Now that we also have a {{PartitionResolver}} the {{routingId}} is optionally computed when needed. Adding an explicit object to represent the key makes for a cleaner abstraction and allows the routing id to be calculated when the key is instantiated.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)