[IGNITE-13618] Provide generated and reflection-based class (de)serializers

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0-alpha2
• Component/s: sql
• Labels: iep-54 ignite-3
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Andrey Mashenkov
• Reporter: Alexey Goncharuk
• Created: 23/Oct/20 12:20
• Updated: 17/Mar/21 10:13
• Resolved: 17/Mar/21 10:13

Description

Motivation.

It may worth having generated serializer code for performance reasons. However, this should be proved with benchmarks.

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.

Issue Links

• contains: IGNITE-13617 Provide an initial implementation for assembling/reading tuples for a given schema
• is a child of: IGNITE-13616 IEP-54 Live schema for tables
• links to: GitHub Pull Request #35