[
https://issues.apache.org/jira/browse/HIVE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13713219#comment-13713219
]
Xuefu Zhang commented on HIVE-1511:
-----------------------------------
[~appodictic] Before noticing this one, I was thinking of Jackson too. Jackson
is pretty good at XML/JSON serialization/de- with reasonably good performance,
and widely adopted, especially for XML/JSON. I used it for java bean
serialization, so am not sure of how well it handles object graph as it's our
case. It's something to figure out.
This new comer seems very impressive in performance, which may not be super
critical in Hive's use case. However, are you suggesting that the serialized
form isn't human-readable? I didn't see the output, so wouldn't know.
> Hive plan serialization is slow
> -------------------------------
>
> Key: HIVE-1511
> URL: https://issues.apache.org/jira/browse/HIVE-1511
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 0.7.0
> Reporter: Ning Zhang
> Attachments: HIVE-1511.patch
>
>
> As reported by Edward Capriolo:
> For reference I did this as a test case....
> SELECT * FROM src where
> key=0 OR key=0 OR key=0 OR key=0 OR key=0 OR key=0 OR key=0 OR key=0
> OR key=0 OR key=0 OR key=0 OR
> key=0 OR key=0 OR key=0 OR key=0 OR key=0 OR key=0 OR key=0 OR key=0
> OR key=0 OR key=0 OR key=0 OR
> ...(100 more of these)
> No OOM but I gave up after the test case did not go anywhere for about
> 2 minutes.
--
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
