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
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: "_", “+”, “-“, “:”, “#”,
“@“
Here is the page of the documentation on region naming:
http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html
I'm guessing that a JIRA for also including a dash was not implemented.
When you find the
JIRA number, please post it on this thread.
On Thu, Jun 30, 201
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 wrote:
> Yes we did discuss adding hyphen in Geode, and we discussed actually
> checking during
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 wrote:
> I found a thread from March of this year where this was discussed an
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 d
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 wrote:
> I'm working on a bug where it is not
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 a
+1
My experience is that most users should have few or no issues using the list
defined by William. In part as we have in the past discouraged the use of other
characters and so it should be rare that someone used something outside this
list.
Vince
Sent from my iPhone
> On Mar 1, 2016, at 1
+1
--
Kareem
On Wed, Mar 2, 2016 at 9:20 AM -0800, "Kirk Lund" wrote:
+1
On Tue, Mar 1, 2016 at 2:35 PM, William Markito wrote:
> Folks, it doesn't look like we have actually finished this thread...
>
> What do you guys think about the following pattern:
> "ABCDEFGHIJKLMNOPQRSTU
+1
On Tue, Mar 1, 2016 at 2:35 PM, William Markito wrote:
> Folks, it doesn't look like we have actually finished this thread...
>
> What do you guys think about the following pattern:
> "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz123456-_" ?
>
> I'm not specifying a regexp to avoid p
That would be changed from now on as it's too much open ended and
troublesome to support in other subsystems such as JMX beans... Note that
"-" is still in the list, other symbols would not be allowed like "+" or
"@" - Which are very odd and should be very rare.
On Tue, Mar 1, 2016 at 2:52 PM, Ani
>From the existing javadoc it looks like, application can have any chars in
region name except the "/".
Changing this one may have implication on existing GemFire customers
In the past we had to make changes in OQL to support chars like "+", "-",
"@"...(since customers used this in their regi
+1
On 2/03/2016 9:35 am, William Markito wrote:
Folks, it doesn't look like we have actually finished this thread...
What do you guys think about the following pattern:
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz123456-_" ?
I'm not specifying a regexp to avoid problems with unicode
Folks, it doesn't look like we have actually finished this thread...
What do you guys think about the following pattern:
"ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz123456-_" ?
I'm not specifying a regexp to avoid problems with unicode and to keep it
only ASCII-only... Stackoveflow has
The public javadocs on Region#getName say:
Returns the name of this region. A region's name
* can be any non-empty String providing it does not
* contain the name separator, a forward slash (/).
Here is the code from LocalRegion that validates the name:
static void validateRegionName(Strin
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
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 wrote:
> I was just looking into a ticket filed because /= was used as the Region
> name and this caused pro
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
Regio
19 matches
Mail list logo
