Re: Namespace validation/requirements

2020-06-11 Thread Micah Kornfield
That seems reasonable to me. FWIW, I opened https://github.com/apache/avro/pull/917 to update the language. Thanks, Micah On Thu, Jun 11, 2020 at 10:31 AM Sean Busbey wrote: > I'm happy to make PR clarifying this. I'm a little bit concerned that if >> validation doesn't exist in Java (and may

Re: Namespace validation/requirements

2020-06-11 Thread Sean Busbey
> > I'm happy to make PR clarifying this. I'm a little bit concerned that if > validation doesn't exist in Java (and maybe other languages today) if we > make the spec stricter it could break users. How has the community handled > issues like this in the past? Something similar happened for the

Re: Namespace validation/requirements

2020-06-05 Thread Ryan Skraba
Hello, it's not a silly question -- it's kind of hidden inside the ./build.sh dist script. Just run ant from inside the ./doc directory and the html files are generated in the ./build/avro-doc-1.11.0-SNAPSHOT/ directory (N.B. not the ./doc/build directory). I don't have ant installed on my machin

Re: Namespace validation/requirements

2020-06-04 Thread Micah Kornfield
This might be a silly question, but how can I build the specification documentation? Is it part of the javadoc build? Sorry i scanned the documentation and couldn't find anything specific. Thanks, Micah On Tue, Jun 2, 2020 at 12:04 AM Micah Kornfield wrote: > Thanks, I should have a PR up in

Re: Namespace validation/requirements

2020-06-02 Thread Micah Kornfield
Thanks, I should have a PR up in the next few days for the spec. On Fri, May 29, 2020 at 12:57 AM Ryan Skraba wrote: > I'm certain that the Java implementation doesn't validate full names > correctly (https://issues.apache.org/jira/browse/AVRO-2659 has a fun > example). This should be an easy f

Re: Namespace validation/requirements

2020-05-29 Thread Ryan Skraba
I'm certain that the Java implementation doesn't validate full names correctly (https://issues.apache.org/jira/browse/AVRO-2659 has a fun example). This should be an easy fix, I'll give it a go. A PR to clarify the spec on this point would be welcome! On Thu, May 28, 2020 at 6:47 PM Micah Kornfi

Re: Namespace validation/requirements

2020-05-28 Thread Micah Kornfield
I'm happy to make PR clarifying this. I'm a little bit concerned that if validation doesn't exist in Java (and maybe other languages today) if we make the spec stricter it could break users. How has the community handled issues like this in the past? Would someone familiar with the Java implemen

Re: Namespace validation/requirements

2020-05-28 Thread Doug Cutting
Yes, the intent was to prohibit namespaces starting with a dot. | ((()*)) was the intended grammar. Doug On Thu, May 28, 2020 at 1:50 AM Ryan Skraba wrote: > Hello! Hmmm... reading through the spec (again), there is a small > ambiguous point! Good catch! > > Specifically, it specifically s

Re: Namespace validation/requirements

2020-05-28 Thread Ryan Skraba
Hello! Hmmm... reading through the spec (again), there is a small ambiguous point! Good catch! Specifically, it specifically says that ".a" is not a valid namespace attribute: "A namespace is a dot-separated sequence of such [non-empty] names. The empty string may also be used as a namespace ..

Namespace validation/requirements

2020-05-27 Thread Micah Kornfield
Hi Avro Dev, I think there is a little bit of ambiguity in the requirements for the namespace component of a full name in the specification [1]. In particular it isn't clear whether namespaces like: ".namespace" should be considered valid (i.e. a "null" namespace followed a valid name). It appear