[
https://issues.apache.org/jira/browse/IGNITE-23625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-23625:
---------------------------------
Priority: Major (was: Minor)
> Add support for Java Records in Ignite 3
> ----------------------------------------
>
> Key: IGNITE-23625
> URL: https://issues.apache.org/jira/browse/IGNITE-23625
> Project: Ignite
> Issue Type: Epic
> Reporter: Tiago Marques Godinho
> Priority: Major
> Labels: ignite-3
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
