ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cameron Steffen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-7176) SqlQuery does not always find matching entries
Date Wed, 02 Jan 2019 22:32:00 GMT

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

Cameron Steffen commented on IGNITE-7176:
-----------------------------------------

[~mk_mgb] Can you clarify the scope of this bug?

> SqlQuery does not always find matching entries
> ----------------------------------------------
>
>                 Key: IGNITE-7176
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7176
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.3, 2.4
>            Reporter: Markus Kinzler
>            Priority: Critical
>             Fix For: 2.7
>
>         Attachments: sqlbug.zip
>
>
> When the @QuerySqlField annotation is put on a custom class, the sql query sometimes
does not find the entry.
> With an cache of 100'000 entries, the problem occurs in about 50% of the test runs for
1 - 2 entries.
> When the entry is not found, no log statement is written and no exception is thrown,
but the result is missing, despite beeing accessible via cache.get(key).
> Note that i could not reproduce the Issue when i rename the class LegaldocAcceptPk to
TestEntityPk.
> A reproducible unit test is attached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message