[
https://issues.apache.org/jira/browse/GEODE-9044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Deppe updated GEODE-9044:
------------------------------
Labels: blocks-1.14.0 pull-request-available (was: pull-request-available)
> 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
>
> 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)
