There is a stated position in the commercial GemFire documentation as follows:
To get the full range of Pivotal GemFire capabilities for your cached data regions, follow GemFire's region naming guidelines: The safest approach when naming your regions is to use only alphanumeric characters and the underscore character and to keep your region names short. This permits you the full range of GemFire region configurations and allow you to perform all available GemFire operations on the region. Follow these guidelines for naming regions: • Do not use the separator slash character ‘ / ’. • Do not begin region names with two underscore characters "__" as this is reserved for internal GemFire use. • To run queries against your data, restrict your region names to alphanumeric characters and the underscore character. For Geode we should probably tighten that up just a bit further by changing the last bullet to: • Restrict your region names to alphanumeric characters and the underscore character. -- Mike Stolz Principal Engineer, GemFire Product Manager Mobile: 631-835-4771 On Thu, Feb 18, 2016 at 2:09 PM, William Markito <[email protected]> wrote: > I don't think we should allow non-alphanumeric region names... And would > be really nice to have a list or a pattern documenting what's valid. > > > On Thu, Feb 18, 2016 at 11:04 AM Kirk Lund <[email protected]> wrote: > > > I was just looking into a ticket filed because /= was used as the Region > > name and this caused problems in JMX ObjectNames. I have two questions: > 1) > > do we really want /= to be a valid Region name? 2) do we have a complete > > list somewhere of all the non-alphanumeric characters that are usable in > > Region names? > > > > -Kirk > > > -- > ~/William >
