[
https://issues.apache.org/jira/browse/IGNITE-27552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053657#comment-18053657
]
Pavel Pereslegin commented on IGNITE-27552:
-------------------------------------------
Merged into feature-branch
([ignite-27612-tuple-implicit-casts|https://github.com/apache/ignite-3/tree/ignite-27612-tuple-implicit-casts]),
> Add support for writing numeric values of tuples with allowed type casting
> ----------------------------------------------------------------------------
>
> Key: IGNITE-27552
> URL: https://issues.apache.org/jira/browse/IGNITE-27552
> Project: Ignite
> Issue Type: Improvement
> Components: sql ai3
> Reporter: Pavel Pereslegin
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> This task is split from IGNITE-26491.
> IGNITE-26491 is about reading values. For example, if the field "ID" in the
> schema has type INT32, It is allowed to read the value using any of the Tuple
> methods:
> {code:java}
> longValue()
> intValue()
> shortValue() // if the value is in range [Float.MIN_VALUE .. Float.MAX_VALUE]
> byteValue() // if the value is in range [Byte.MIN_VALUE .. Byte.MAX_VALUE]
> {code}
> Other conversion rules are described in the *UPDATE* section of IGNITE-26491
> description.
> Current issue is about *writing values*.
> For consistency the same rules must be applied when writing values.
> For example, the java.lang.Byte value must be allowed to be writen into INT64
> field and Long-value into INT8 if it firs into it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
