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 2011/08/24 00:49:29 UTC
[jira] [Commented] (AVRO-816) Schema Comparison Utils
[ https://issues.apache.org/jira/browse/AVRO-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089838#comment-13089838 ]
Doug Cutting commented on AVRO-816:
-----------------------------------
Where are we with this issue? Scott, what changes would you like to see in this patch?
> Schema Comparison Utils
> -----------------------
>
> Key: AVRO-816
> URL: https://issues.apache.org/jira/browse/AVRO-816
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Joe Crobak
> Assignee: Joe Crobak
> Priority: Minor
> Fix For: 1.6.0
>
> Attachments: AVRO-816.patch, AVRO-816.patch, AVRO-816.patch, AVRO-816.patch
>
>
> From my post on the mailing list, and Doug's response:
> {quote}
> On 05/05/2011 10:29 AM, Joe Crobak wrote:
> > We've recently come across a situation where we have two data files with
> > different schemas that we'd like to process together using
> > GenericDatumReader. One schema is promotable to the other, but not vice
> > versa. We'd like to programmatically determine which of the schemas to
> > use. I did a brief look through javadoc and tests, and I couldn't find
> > any examples of checking if one schema is promotable to the other. Has
> > anyone else come across this?
> >
> > For some context, we're considering patching AvroStorage [1] to remove
> > the assumption that all files have the same schema. In our case, our
> > schema has evolved in that a field that was an int was promoted to a long.
> A boolean method that tells you if one schema is promotable to another
> would work in this case, but would not help in cases where, e.g.,
> different fields had changed in different versions. For example, in
> branched development, two branches might each add a distinct symbol to
> an enum. So I think you might be better off with a method that, given
> two schemas, returns their superset, a schema that can read data written
> by either.
> Such a method does not yet exist in Avro, but should not be difficult to
> add. Please file an issue in Jira if this sounds of interest.
> Doug
> {quote}
> I think it would be useful to have both of the methods that Doug mentioned in some sort of schema utils class.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira