You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Davor Bonaci (JIRA)" <ji...@apache.org> on 2016/05/03 09:07:13 UTC

[jira] [Issue Comment Deleted] (BEAM-232) Update AvroIO JavaDoc to Mention Registering Coder

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

Davor Bonaci updated BEAM-232:
------------------------------
    Comment: was deleted

(was: Registering a coder is somewhat orthogonal to this section.

The model requirement is that every PCollection has to have a coder, including the output PCollection of AvroIO. Now, this requirement is very generic, pipeline wide, and can be satisfied in several ways. Registering a coder is just one of them.

With this information, I'd probably close this one. Does that sound right to you, [~eljefe6aa]?)

> Update AvroIO JavaDoc to Mention Registering Coder
> --------------------------------------------------
>
>                 Key: BEAM-232
>                 URL: https://issues.apache.org/jira/browse/BEAM-232
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Jesse Anderson
>            Assignee: Davor Bonaci
>
> The AvroIO docs say:
> {quote}To read specific records, such as Avro-generated classes, provide an Avro-generated class type.{quote}
> They don't mention that you need to register a coder in order for the specific records class to not get a RuntimeException.
> The JavaDocs should be update to say you need to register and the code snippets in the JavaDocs should be updated to at least mention this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)