For Aurora, might be a good idea to browse the code or ask an Aurora dev to point you to their TaskID construction code.
On Thu, Feb 20, 2014 at 3:56 PM, Dominic Hamon <[email protected]> wrote: > Hello > > Until now, TaskIDs have been completely freeform. This, however, has led > to some bugs that we'd like to tackle by restricting the characters that > are allowed in the TaskID. The bug to follow is > MESOS-361<https://issues.apache.org/jira/browse/MESOS-361> > . > > One proposal is to ensure there are no characters in the ID that might > cause issues with paths. This would include slashes, ampersands, etc. > > The other proposal is to restrict the character set to a minimal > alphanumeric, hyphen, underscore set. > > I'd like to get a sense of what characters you feel you need to have in > TaskIDs as users. > > Thanks > > -- > Dominic Hamon | @mrdo | Twitter > *There are no bad ideas; only good ideas that go horribly wrong.* >
