You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Thiruvalluvan M. G. (JIRA)" <ji...@apache.org> on 2010/02/01 18:46:19 UTC
[jira] Commented: (AVRO-208) java specific compiler doesn't check
for ambiguous enums
[ https://issues.apache.org/jira/browse/AVRO-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828194#action_12828194 ]
Thiruvalluvan M. G. commented on AVRO-208:
------------------------------------------
ValidatingEncoder/Decoder and ResolvingDecoder will have problem with empty enums. The encoder/decoder will expect a call to write/read enum. But with every value, it'll throw an error stating the value is invalid. I guess GenericDatumWriter/Reader will have the problem as well.
I think it's best not to allow empty enums.
> java specific compiler doesn't check for ambiguous enums
> --------------------------------------------------------
>
> Key: AVRO-208
> URL: https://issues.apache.org/jira/browse/AVRO-208
> Project: Avro
> Issue Type: Bug
> Components: spec
> Affects Versions: 1.2.0
> Reporter: Patrick Hunt
> Assignee: Doug Cutting
> Fix For: 1.3.0
>
> Attachments: AVRO-208.patch
>
>
> the java specific compiler flags ambiguous unions but not enums
> "response": {"name":"E1", "type":"enum", "symbols":["AA", "AA"]},
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.