Ryan King wrote:
We should reserve some space, like avro.*, rather than having to do it
one at a time.
+1 This sounds like a good idea.
Questions:
- Should we rename all existing keywords to this namespace? My vote
is yes, now is the time to do this.
- Should the namespace be "avro.*" or "org.apache.avro.*"? The
fully-qualified name would be more consistent with Avro schema and
protocol namespaces, but it might prove awkward should Avro ever become
a standard independent of the ASF's implementation. As a vaguely
related example, I expect that Avro will become a top-level project at
Apache this year, and am pleased that our Java implementation is already
in org.apache.avro, not org.apache.hadoop.avro. I think we should thus
try to keep the format specification independent of the ASF, and use
"avro.*" here.
Doug
