Here's the DNS regexp (ignoring string length)
/**
* Pattern of a single entry in the registry path. : {@value}.
* <p>
* This is what constitutes a valid hostname according to current RFCs.
* Alphanumeric first two and last one digit, alphanumeric
* and hyphens allowed in between.
* <p>
* No upper limit is placed on the size of an entry.
*/
String VALID_PATH_ENTRY_PATTERN =
"([a-z0-9]|[a-z0-9][a-z0-9\\-]*[a-z0-9])";
We should maybe have a "warn @" regexp (underscores), and a fail-fast for the
things we know won't work" (spaces, etc)
> On 14 Jan 2016, at 10:07, Jon Maron <jma...@hortonworks.com> wrote:
>
> We may want to eliminate underscores given their issues with DNS etc.
>
>
>> On Jan 14, 2016, at 12:26 PM, Gour Saha <gs...@hortonworks.com> wrote:
>>
>> The current acceptable name pattern is [a-z][a-z0-9_-]* (SliderUtils.java
>> - clusternamePattern). It includes the dash (-).
>>
>> While Jon experiments with your package, just wondering your app works
>> fine when you get rid of the dash, right?
>>
>> -Gour
>>
>>> On 1/14/16, 8:35 AM, "Jon Maron" <jma...@hortonworks.com> wrote:
>>>
>>> Sorry - got pulled off on some other tasks. I¹ll try to take a look over
>>> the next day or so.
>>>
>>>> On Jan 14, 2016, at 11:31 AM, Manoj Samel <manojsamelt...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> Any update on this ? Did you get a chance to try the memcache with the
>>>> component name I used above ?
>>>>
>>>> Thanks,
>>>>
>>>> Manoj
>>>>
>>>> On Tue, Jan 12, 2016 at 4:37 PM, Steve Loughran <ste...@hortonworks.com>
>>>> wrote:
>>>>
>>>>>
>>>>>> On 12 Jan 2016, at 12:14, Jon Maron <jma...@hortonworks.com> wrote:
>>>>>>
>>>>>> OK. So was there a Œ-Œ or some other character in your component
>>>>>> name?
>>>>> A Œ-Œ should work. The component names are currently expected to
>>>>> follow a
>>>>> naming convention that allows for DNS compatible names, and dashes are
>>>>> included in that character set. The fact that the endpoint did not
>>>>> appear
>>>>> may be related to some other issue. The AM logs may help here as well.
>>>>>
>>>>>
>>>>> We should be checking component names early on, because it would really
>>>>> break bits of the REST API too.
>>
>>
>
