[
https://issues.apache.org/jira/browse/IGNITE-13618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303218#comment-17303218
]
Alexey Goncharuk commented on IGNITE-13618:
-------------------------------------------
[~amashenkov] I've added a README file to the module with schema management
description from the IEP. Good to merge from my side.
> Provide generated and reflection-based class (de)serializers
> ------------------------------------------------------------
>
> Key: IGNITE-13618
> URL: https://issues.apache.org/jira/browse/IGNITE-13618
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Alexey Goncharuk
> Assignee: Andrey Mashenkov
> Priority: Major
> Labels: iep-54, ignite-3
> Fix For: 3.0.0-alpha2
>
> Attachments: benchmark-results.txt
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> h3. Motivation.
> It may worth having generated serializer code for performance reasons.
> However, this should be proved with benchmarks.
> h3. Description.
> Let's prototype object serializer for type-system described in IEP-54, and
> benchmark them to check if generated code approach is a better one.
> * As we go with Java11 then VarHandles must be used instead of Unsafe.
> * For generated serializer we can use: JDK compiler + Javapoet project (Java
> code generator) or Janino compiler or even Prestodb-bytecode module of
> PrestoDB project
> *UPD*: JDK compile is too slow, Janino doesn't support Java9+ and VarHandles,
> Prestodb-bytecode has an unwanted Guava dependency.
> So, forking Prestodb without Guava looks like a preferable way.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
