beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davor Bonaci (JIRA)" <>
Subject [jira] [Commented] (BEAM-232) Update AvroIO JavaDoc to Mention Registering Coder
Date Tue, 03 May 2016 07:07:13 GMT


Davor Bonaci commented on BEAM-232:

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:
>             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

View raw message