Ran into an issue today with avro 1.5.3 where someone defined a enum
as a inner class:

public class Foo {
   public static enum Bar { ONE, TWO }
}

And Schema.validateName complained about the name Foo$Bar.  Is there
any reason to have this restriction?

The spec http://avro.apache.org/docs/1.5.3/spec.html#Names
states that names must:

          
* start with [A-Za-z_]
          
* subsequently contain only [A-Za-z0-9_]


Unfortunately, Java inner classes contain $.

Sometimes, avro uses $ internally to disambiguate names, since if it
creates a field or method with '$' in it that can't conflict with a user
created one.  

Can you open a JIRA to discuss this limitation further?

Thanks!

-Scott
On 8/30/11 10:26 PM, "Chris Wilkes" <[EMAIL PROTECTED]> wrote:

>Ran into an issue today with avro 1.5.3 where someone defined a enum
>as a inner class:
>
>public class Foo {
>   public static enum Bar { ONE, TWO }
>}
>
>And Schema.validateName complained about the name Foo$Bar.  Is there
>any reason to have this restriction?