[GEODE-9044] Introduce RedisKey as key object for RedisData entries

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.14.0, 1.15.0
• Component/s: redis
• Labels: blocks-1.14.0​ pull-request-available
• Assignee: Jens Deppe
• Reporter: Jens Deppe
• Created: 17/Mar/21 14:09
• Updated: 03/Sep/21 02:25
• Resolved: 23/Mar/21 18:51

Description

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.

Issue Links

• links to: GitHub Pull Request #6146
• links to: GitHub Pull Request #6173