You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2010/12/29 22:57:46 UTC
[jira] Commented: (AVRO-638) make reflect, specific and generic
data compatible
[ https://issues.apache.org/jira/browse/AVRO-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975926#action_12975926 ]
Doug Cutting commented on AVRO-638:
-----------------------------------
With AVRO-669 committed, reflect data is now a superset of specific, and specific is a superset of generic. The only potential source of incompatibility is that ReflectDatumReader always creates java.lang.String for string data, while SpecificDatumReader and GenericDatumReader always create org.apache.avro.util.Utf8.
Unless there are objections, I will close this as fixed.
> make reflect, specific and generic data compatible
> --------------------------------------------------
>
> Key: AVRO-638
> URL: https://issues.apache.org/jira/browse/AVRO-638
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Doug Cutting
> Assignee: Doug Cutting
> Fix For: 1.5.0
>
>
> With AVRO-605 and AVRO-86, reflect, specific and generic are nearly compatible. Records, primitive types, maps and enums now share common representations. AVRO-637 would add arrays. After that I think only some issues with union type dispatch would remain. Then specific and/or generic data could be arbitrarily intermixed with reflect data with ReflectDatumReader and ReflectDatumWriter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.