[
https://issues.apache.org/jira/browse/CRUNCH-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510740#comment-13510740
]
Josh Wills commented on CRUNCH-124:
-----------------------------------
@Ashish will do in my next rev.
@Gabriel my thinking was that the common case for consuming an Avro file was
one where some kind of external schema was already defined and the generated
Java code implemented SpecificRecord. To cut down on the number of functions,
we could opt to remove the type restrictions on the method and use
Avros.records(clazz) to generate the PType, although we'd need the docs to be
explicit about what was going on there. Is that your preference? I'm also
curious what other Avro users think is the right behavior here.
> Javadoc the From, To, and At static methods and add convenience methods for
> sequenceFiles
> -----------------------------------------------------------------------------------------
>
> Key: CRUNCH-124
> URL: https://issues.apache.org/jira/browse/CRUNCH-124
> Project: Crunch
> Issue Type: Improvement
> Components: IO
> Reporter: Josh Wills
> Attachments: CRUNCH-124.patch
>
>
> Aside from org.apache.crunch.*, the o.a.c.io.(From|To|At) methods are among
> the most user-facing classes we have. We should javadoc them thoroughly and
> add more convenience methods that make them easier to get started with for
> new Crunch users.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
