[
https://issues.apache.org/jira/browse/CRUNCH-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448492#comment-13448492
]
Rahul Sharma commented on CRUNCH-52:
------------------------------------
Josh, thanks for your insights. But the original issue is related to the
To.textFile(...) API's that we have. If we write back using Strings then I the
issue will be still open.
I believe in such a case I can create additional variants having two args that
can cater to Avro types and we would also have the single args API for backward
comparability.
Alternatively I had a look at At.textFile APIs, these APIs can cater to the
issue. We can keep the To APIs for Strings and if people want to handle ptypes
then the can use the At APIs. BTW just for my understanding, the To and At
APIs look very much similar. I think they can be used quite interchangeably for
writing data, any insights on them ?
> Writing to a text file with avro types fills a file with the tostring of
> AvroWrapper
> ------------------------------------------------------------------------------------
>
> Key: CRUNCH-52
> URL: https://issues.apache.org/jira/browse/CRUNCH-52
> Project: Crunch
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Robert Chu
> Attachments: CRUNCH-52.patch
>
>
> Currently when writing a pcollection to a text file (provided by
> To.textFile(...)) TextOutputFormat doesn't unwrap avro types.
--
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
