We already discussed this on the previous thread and got general consensus on getting "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz12345678 90_-" for Geode... Anything other than this can be problematic for JMX and other components that will then require special treatment to handle unusual chars.
If any user is coming from GemFire , they still can use snapshots to export/import data into the new regions. I'd also recommend enforcing the rules for region creation in all possible APIs, for consistency... (GFSH, cache.xml, RegionFactory...) On Thu, Jun 30, 2016 at 4:49 PM, Anilkumar Gingade <aging...@pivotal.io> wrote: > Here is what GemFire docs states about region names: > > > http://gemfire.docs.pivotal.io/docs-gemfire/latest/basic_config/data_regions/region_naming.html > > But again, we have supported other chars as part of region names... > > The Query engine allows/detects region name with: "_", “+”, “-“, “:”, “#”, > “@“, “$”. > > -Anil. > > > > > On Thu, Jun 30, 2016 at 11:03 AM, Kevin Duling <kdul...@pivotal.io> wrote: > > > I'm working on a bug where it is not possible to delete a region that > has a > > hyphen in it. E.g., the region was created with: > > > > create region --name=not-good --type=REPLICATE > > > > I've a solution done, but see this as an opportunity to add a test for > > other special characters. Is there a list of valid and invalid > characters > > for a region name? > > > -- ~/William
