[ https://issues.apache.org/jira/browse/HIVE-22944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
László Bodor updated HIVE-22944: -------------------------------- Fix Version/s: 4.0.0 > Upgrade to Kryo5 > ---------------- > > Key: HIVE-22944 > URL: https://issues.apache.org/jira/browse/HIVE-22944 > Project: Hive > Issue Type: Improvement > Reporter: László Bodor > Assignee: László Bodor > Priority: Major > Labels: pull-request-available > Fix For: 4.0.0 > > Attachments: HIVE-22944.01.patch, kryo4_vs_5_benchmark.log > > Time Spent: 2h 40m > Remaining Estimate: 0h > > Maybe we should consider upgrading to kryo5 (plan ser/deser). Not sure about > performance benefits, but looking at the code, e.g. FieldSerializer in Kryo5 > seems to let us extend it easier (less private fields), which could be a > benefit if we want to change its behavior, e.g. defining different logic for > different fields of an object. > Kryo 4 FieldSerializer: > https://github.com/EsotericSoftware/kryo/blob/kryo-4/src/com/esotericsoftware/kryo/serializers/FieldSerializer.java > Kryo 5 FieldSerialier: > https://github.com/EsotericSoftware/kryo/blob/master/src/com/esotericsoftware/kryo/serializers/FieldSerializer.java > UPDATE: currently we are at kryo 5.0.3 > TODO: why kryo-shaded artifact has been used so far? > https://javalibs.com/artifact/com.esotericsoftware/kryo-shaded > "This contains the shaded reflectasm jar to prevent conflicts with other > versions of asm." -- This message was sent by Atlassian Jira (v8.3.4#803005)