[
https://issues.apache.org/jira/browse/GEODE-9044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17307354#comment-17307354
]
ASF subversion and git services commented on GEODE-9044:
--------------------------------------------------------
Commit f91c577f1751d98ed4bc8e8569fd7d88a01c224e in geode's branch
refs/heads/support/1.14 from Jens Deppe
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=f91c577 ]
GEODE-9044: Introduce RedisKey as key object for RedisData entries (#6146)
(#6173)
- Refactor all redis key references to use RedisKey
- RedisKey extends ByteArrayWrapper and adds a routingId integer value.
This is used by the RedisPartitionResolver to map entries to buckets.
(cherry picked from commit 3a9baeff35c362cb6ec5df949553764eefcdc6a2)
> 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)
