[IGNITE-23625] Add support for Java Records in Ignite 3

• Type: Epic
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Labels: ignite-3
• Epic Name: Support Java Records
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Unassigned
• Reporter: Tiago Marques Godinho
• Created: 07/Nov/24 09:31
• Updated: 07/Nov/24 10:25

Description

Records, which were introduced in Java 16, provide a compelling alternative to POJOs for data-carrying purposes. They significantly reduce boilerplate and in general, provide a better developer experience.
As a result, Ignite 3 should support records on their main public APIs.

The biggest barriers I found in our codebase for supporting records are:

• Strict requirement for default constructors in our models/data carrier classes.
• A slight misalignment in the policy for instantiating these classes. PojoMarshaller first creates the instances and then injects the fields, which should be the opposite for records.

They seem pretty simple to overcome.