You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2026/01/21 13:59:00 UTC

[jira] [Commented] (IGNITE-27537) Sql. Support equals/hashCode in public SqlRow

    [ https://issues.apache.org/jira/browse/IGNITE-27537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18053324#comment-18053324 ] 

Pavel Pereslegin commented on IGNITE-27537:
-------------------------------------------

Fixed in IGNITE-26491

> Sql. Support equals/hashCode in public SqlRow
> ---------------------------------------------
>
>                 Key: IGNITE-27537
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27537
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql ai3
>            Reporter: Pavel Pereslegin
>            Priority: Major
>              Labels: ignite-3
>
> Currently public {{SqlRow}} class doesn't implement equals/hashCode. 
> All other public {{Tuple}} implementations implement the {{equals}}/{{hashCode}} methods and allow each tuple to be compared to another.
> Additionally, such tuples can be used to be added to a Map and passed to methods like putAll (table views), so without equals/hashCode support, unexpected behavior is possible.
> Reproducer:
> {code}
> SqlRow row1 = igniteSql().execute(null, "SELECT 1").next();
> SqlRow row2 = igniteSql().execute(null, "SELECT 1").next();
> assertThat(row1, equalTo(row2)); // fails
> {code}
> p.s. please unmute disabled tests related to this issue



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