[jira] [Assigned] (IGNITE-15254) Tuple API should be decoupled from Table

["Andrey Mashenkov (Jira)" <ji...@apache.org>]

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

Andrey Mashenkov reassigned IGNITE-15254:
-----------------------------------------

    Assignee: Andrey Mashenkov

> Tuple API should be decoupled from Table
> ----------------------------------------
>
>                 Key: IGNITE-15254
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15254
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 3.0.0-alpha2
>            Reporter: Valentin Kulichenko
>            Assignee: Andrey Mashenkov
>            Priority: Major
>              Labels: iep-54, ignite-3
>             Fix For: 3.0.0-alpha3
>
>
> Currently, a tuple can be created via a builder which can be acquired from a table. This is counterintuitive because in the general case, a tuple does not have a direct relation with a particular table (think of a tuple that is a part of a SQL result set, for example).
> Instead, we should treat Tuple as a simple data structure that can be reused for multiple purposes. That said, let's do the following changes to the API:
> * Make Tuple mutable (i.e., add setters).
> * Get rid of the builder, as it becomes redundant.
> * Move tuple creation from the Table API to Ignite API.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)