[jira] Resolved: (AVRO-603) SpecificDatumReader requires the reader's schema to be set manually

["Doug Cutting (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AVRO-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting resolved AVRO-603.
-------------------------------

    Hadoop Flags: [Reviewed]
        Assignee: Stu Hood
      Resolution: Fixed

I just committed this.  Thanks, Stu!

> SpecificDatumReader requires the reader's schema to be set manually
> -------------------------------------------------------------------
>
>                 Key: AVRO-603
>                 URL: https://issues.apache.org/jira/browse/AVRO-603
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>            Reporter: Stu Hood
>            Assignee: Stu Hood
>            Priority: Minor
>         Attachments: 0001-Rename-parameters-add-simple-Javadocs-and-add-Specif.patch
>
>
> Since SpecificDatumReader has actual objects with schemas attached to them, it would seem that you wouldn't need to set the reader's schema: the default constructor only takes one schema argument, so it seems to support this, but behind the scenes, it sets the readers/writers to the same schema.
> Additionally, since DatumReader and its implementations use the terms 'expected' and 'actual' to refer to the 'reader' and 'writer' schemas, determining that you need to set the reader's schema requires a code dive, rather than a glance at the javadocs.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.