[
https://issues.apache.org/jira/browse/AVRO-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702523#action_12702523
]
Doug Cutting commented on AVRO-18:
----------------------------------
Like records, enums should probably be named. So an enum might look like:
{code}
{"name": "Foo", "type": "enum", "values": ["a", "b", "c"]}
{code}
Do we need to permit folks to specify explicit integer values, e.g.:
{code}
{"name": "Foo", "type": "enum", "values": [{"a",-1}, {"b", 0}, {"c", 1}]}
{code}
In Java's specific and reflect API's we can represent enums as Java enums.
In Java's generic API we might represent enum values as interned strings by
default.
> add enum type
> -------------
>
> Key: AVRO-18
> URL: https://issues.apache.org/jira/browse/AVRO-18
> Project: Avro
> Issue Type: New Feature
> Components: spec
> Reporter: Doug Cutting
>
> Avro schemas should support enum types.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
