[
https://issues.apache.org/jira/browse/CRUNCH-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510770#comment-13510770
]
Gabriel Reid commented on CRUNCH-124:
-------------------------------------
[~jwills] I think the way it is now will be fine. You're probably right that
the most common use-case is using SpecificRecord, and it's not that big of a
bother to provide the PType for the other use cases when necessary.
In my Avro experience, I've never really relied on generic records, although in
the past I did use the reflection-based Avro serialization (together with
Lombok-annotated classes) quite a bit to do quick prototyping, which basically
gives you the same as working with SpecificRecords without the hassle of
creating a schema or generating classes. I think that this was mostly motivated
by laziness, and I don't think it was that common of a use case.
> 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
