Do you know if a Jira ticket was opened on it?  I'm currently working on
https://issues.apache.org/jira/browse/GEODE-1615 and would like to link to
it.

On Thu, Jun 30, 2016 at 12:38 PM, Michael Stolz <[email protected]> wrote:

> Yes we did discuss adding hyphen in Geode, and we discussed actually
> checking during create.
>
> --
> Mike Stolz
> Principal Engineer, GemFire Product Manager
> Mobile: 631-835-4771
>
> On Thu, Jun 30, 2016 at 3:30 PM, Kevin Duling <[email protected]> wrote:
>
> > I found a thread from March of this year where this was discussed and '-'
> > is also included in that list.
> >
> > Shouldn't the creation of a region with an invalid character raise an
> > exception?  I'm finding that I can create and list regions with a variety
> > of non-alphanumeric characters.  But I can only destroy a subset of
> those.
> >
> >  It appears to be because some are created with quotes around the region
> > name.
> >
> > E.g.,
> >
> > service=Region, name=/good, type=Member
> > service=Region, name="/not*good", type=Member
> >
> > The name lookup fails in the Destroy call.  The rule that applied the
> > quotes for /not*good during Create isn't applied in Destroy
> >
> > On Thu, Jun 30, 2016 at 12:06 PM, Michael Stolz <[email protected]>
> wrote:
> >
> > > The only characters that should be used in Region names are
> > > ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz1234567890_
> > >
> > > --
> > > Mike Stolz
> > > Principal Engineer, GemFire Product Manager
> > > Mobile: 631-835-4771
> > >
> > > On Thu, Jun 30, 2016 at 2:03 PM, Kevin Duling <[email protected]>
> > 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?
> > > >
> > >
> >
>

Reply via email to