[
https://issues.apache.org/jira/browse/AVRO-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828205#action_12828205
]
Doug Cutting commented on AVRO-208:
-----------------------------------
> ValidatingEncoder/Decoder and ResolvingDecoder will have problem with empty
> enums.
It is impossible to serialize an empty enum with any encoder/decoder, no? But
automated code might generate, e.g., an empty enum in a union with null, and
only ever emit the null. So having a schema with an empty enum is currently
possible, but reading or writing a value whose type is an empty enum will
always fail. Does the value of catching this earlier, at schema parse time,
outweigh the cost of prohibiting empty enums in contexts where they're not read
or written? I don't feel strongly one way or the other.
> 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.