[
https://issues.apache.org/jira/browse/HIVE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757736#comment-13757736
]
Leo Romanoff commented on HIVE-1511:
------------------------------------
Just FYI, Kryo's FieldSerializer provides methods that allow you to exclude
certain fields from (de)serialization, as if they are not present. This way you
can make certain fields "transient" from the serialization point of view, even
if they are not really transient in the Java sense.
I don't know if it would help you, but you could try to do the following right
after creation of Kryo instances and registration of classes (i.e.
kryo.register(My.class)) using those instances:
FieldSerializer ser = (FieldSerializer)kryo.getSerializer(MySpecialClass.class);
ser.removeField("fieldName");
// Now you can use your Kryo instance and it won't (de)serialize the field
called fieldName
-Leo
> 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, 0.11.0
> Reporter: Ning Zhang
> Assignee: Mohammad Kamrul Islam
> Attachments: failedPlan.xml, generated_plan.xml, HIVE-1511.10.patch,
> HIVE-1511.11.patch, HIVE-1511.4.patch, HIVE-1511.5.patch, HIVE-1511.6.patch,
> HIVE-1511.7.patch, HIVE-1511.8.patch, HIVE-1511.9.patch, HIVE-1511.patch,
> HIVE-1511-wip2.patch, HIVE-1511-wip3.patch, HIVE-1511-wip4.patch,
> HIVE-1511.wip.9.patch, HIVE-1511-wip.patch, KryoHiveTest.java, run.sh
>
>
> 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
