geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Krone (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-2906) Users need easy co-location of entries on partitioned regions
Date Thu, 11 May 2017 18:18:04 GMT

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

Fred Krone updated GEODE-2906:
------------------------------
    Description: 
Implement a dynamic PartitionResolver that takes a String key and uses a '.' as the separator
between the actual key and the partitioning key, returning the partitioning key when called.


The actual key would be the entire string, the partitioning key would be everything after
the last '.' unless there are no dots in which case it is the whole String (which is the default
without a PartitionResolver).

Requirements:
Make configurable via GFSH, cache.xml, or programmatically
-- Allow them to define their own resolver token
Make it work from the client


  was:
Implement a dynamic PartitionResolver that takes a String key and uses a '.' as the separator
between the actual key and the partitioning key, returning the partitioning key when called.


The actual key would be the entire string, the partitioning key would be everything after
the last '.' unless there are no dots in which case it is the whole String (which is the default
without a PartitionResolver).


> Users need easy co-location of entries on partitioned regions
> -------------------------------------------------------------
>
>                 Key: GEODE-2906
>                 URL: https://issues.apache.org/jira/browse/GEODE-2906
>             Project: Geode
>          Issue Type: Improvement
>          Components: regions
>            Reporter: Fred Krone
>
> Implement a dynamic PartitionResolver that takes a String key and uses a '.' as the separator
between the actual key and the partitioning key, returning the partitioning key when called.

> The actual key would be the entire string, the partitioning key would be everything after
the last '.' unless there are no dots in which case it is the whole String (which is the default
without a PartitionResolver).
> Requirements:
> Make configurable via GFSH, cache.xml, or programmatically
> -- Allow them to define their own resolver token
> Make it work from the client



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message