[jira] [Assigned] (IGNITE-27612) Allow numeric primitive type conversion when reading values from and writing values to Tuple.

["Pavel Pereslegin (Jira)" <ji...@apache.org>]

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

Pavel Pereslegin reassigned IGNITE-27612:
-----------------------------------------

    Assignee: Pavel Pereslegin

> Allow numeric primitive type conversion when reading values from and writing values to Tuple.
> ---------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-27612
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27612
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql ai3
>            Reporter: Pavel Pereslegin
>            Assignee: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>         Attachments: TupleReadValueBenchmark.java
>
>
> Allow numeric primitive type conversion when reading values from and writing values to Tuple.
> The behavior of the embedded client is inconsistent with the thin client when trying to read a narrower integer type from tuple that contains long value.
> We want to make the behavior consistent in all clients:
>  # align the behavior with the column upgrade rules
>  # relax current validation to support downcast where possible because we don't want to break column upgrade scenarios
> See more details in *UPDATE* section of IGNITE-26491
> The implementation was divided into the following stages:
> * IGNITE-26491 - align reading behavior
> * IGNITE-27552 - align writing behavior
> * IGNITE-27577 - unify the message text of ClassCastException
> the implementation is going on in a separate feature-branch ([ignite-27612-tuple-implicit-casts|https://github.com/apache/ignite-3/tree/ignite-27612-tuple-implicit-casts]),
> Once all the stages are completed, the feature-branch will need to be merged into the main branch and this ticket can be closed.



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