You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Maksim Myskov (Jira)" <ji...@apache.org> on 2024/10/08 17:09:00 UTC

[jira] [Assigned] (IGNITE-23093) Java Client: Nested objects automatic conversion

     [ https://issues.apache.org/jira/browse/IGNITE-23093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maksim Myskov reassigned IGNITE-23093:
--------------------------------------

    Assignee: Maksim Myskov

> Java Client: Nested objects automatic conversion
> ------------------------------------------------
>
>                 Key: IGNITE-23093
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23093
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Aleksandr
>            Assignee: Maksim Myskov
>            Priority: Major
>              Labels: ignite-3
>
> Given nested tuples supported in Compute API, we can use this mechanism to represent nested user objects as "tuple of tuples". As a result of this ticket I should be able to define complex object that contains the mixture of native types and tuples. And this object is automatically converted into/from tuple, so I do not need to define marshallers for such objects.
> After the java client part is done, the tickets for other clients are created.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)