[
https://issues.apache.org/jira/browse/PIG-2641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580760#comment-13580760
]
Russell Jurney commented on PIG-2641:
-------------------------------------
Thanks, Jeremy. You're growing over there :)
The current patch for PIG-1914 is against Piggybank, and I think it should
instead alter the JsonStorage builtin. Is there a way to do this so that
backwards compatibility is not broken?
I also like the idea of including ordering in a field. We can return the json
in a sorted fashion as well, but anything parsing it is likely to mess up
order. Not our problem?
Question: has there been the expectation that the json output of the current
JsonStorage builtin will or can be read by external tools? If not, do we need
to do anything other than ensure that new pig can read the old format to
maintain backwards compatibility? If so... we're breaking compatibility. I
suspect no guarantee was given, but is it relied on in practice?
> Create toJSON function for all complex types: tuples, bags and maps
> -------------------------------------------------------------------
>
> Key: PIG-2641
> URL: https://issues.apache.org/jira/browse/PIG-2641
> Project: Pig
> Issue Type: New Feature
> Components: piggybank
> Affects Versions: 0.12
> Environment: Foggy. Damn foggy.
> Reporter: Russell Jurney
> Assignee: Russell Jurney
> Labels: chararray, fun, happy, input, json, output, pants, pig,
> piggybank, string, wonderdog
> Fix For: 0.12
>
> Attachments: PIG-2641-2.patch, PIG-2641-3.patch, PIG-2641-4.patch,
> PIG-2641.patch
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> It is a travesty that there are no UDFs in Piggybanks that, given an
> arbitrary Pig datatype, return a JSON string of same. I intend to fix this
> problem.
--
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
