[jira] [Updated] (IGNITE-7176) SqlQuery does not always find matching entries
[ https://issues.apache.org/jira/browse/IGNITE-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7176: Component/s: sql > 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 > 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)
[jira] [Updated] (IGNITE-7176) SqlQuery does not always find matching entries
[ https://issues.apache.org/jira/browse/IGNITE-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7176: Fix Version/s: (was: 2.7) > 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 > 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)
[jira] [Updated] (IGNITE-7176) SqlQuery does not always find matching entries
[ https://issues.apache.org/jira/browse/IGNITE-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-7176: Fix Version/s: (was: 2.8) 2.7 > SqlQuery does not always find matching entries > -- > > Key: IGNITE-7176 > URL: https://issues.apache.org/jira/browse/IGNITE-7176 > Project: Ignite > Issue Type: Bug >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)
[jira] [Updated] (IGNITE-7176) SqlQuery does not always find matching entries
[ https://issues.apache.org/jira/browse/IGNITE-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-7176: Fix Version/s: (was: 2.7) 2.8 > SqlQuery does not always find matching entries > -- > > Key: IGNITE-7176 > URL: https://issues.apache.org/jira/browse/IGNITE-7176 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.3, 2.4 >Reporter: Markus Kinzler >Priority: Critical > Fix For: 2.8 > > 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)
[jira] [Updated] (IGNITE-7176) SqlQuery does not always find matching entries
[ https://issues.apache.org/jira/browse/IGNITE-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-7176: --- Fix Version/s: (was: 2.6) 2.7 > SqlQuery does not always find matching entries > -- > > Key: IGNITE-7176 > URL: https://issues.apache.org/jira/browse/IGNITE-7176 > Project: Ignite > Issue Type: Bug >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)
[jira] [Updated] (IGNITE-7176) SqlQuery does not always find matching entries
[ https://issues.apache.org/jira/browse/IGNITE-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Kinzler updated IGNITE-7176: --- Fix Version/s: 2.6 > SqlQuery does not always find matching entries > -- > > Key: IGNITE-7176 > URL: https://issues.apache.org/jira/browse/IGNITE-7176 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.3, 2.4 >Reporter: Markus Kinzler >Priority: Critical > Fix For: 2.6 > > 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)
[jira] [Updated] (IGNITE-7176) SqlQuery does not always find matching entries
[ https://issues.apache.org/jira/browse/IGNITE-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Kinzler updated IGNITE-7176: --- Affects Version/s: 2.4 > SqlQuery does not always find matching entries > -- > > Key: IGNITE-7176 > URL: https://issues.apache.org/jira/browse/IGNITE-7176 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.3, 2.4 >Reporter: Markus Kinzler >Priority: Critical > 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)
[jira] [Updated] (IGNITE-7176) SqlQuery does not always find matching entries
[ https://issues.apache.org/jira/browse/IGNITE-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Kinzler updated IGNITE-7176: --- Priority: Critical (was: Major) > SqlQuery does not always find matching entries > -- > > Key: IGNITE-7176 > URL: https://issues.apache.org/jira/browse/IGNITE-7176 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.3, 2.4 >Reporter: Markus Kinzler >Priority: Critical > 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)
[jira] [Updated] (IGNITE-7176) SqlQuery does not always find matching entries
[ https://issues.apache.org/jira/browse/IGNITE-7176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Kinzler updated IGNITE-7176: --- Attachment: sqlbug.zip > SqlQuery does not always find matching entries > -- > > Key: IGNITE-7176 > URL: https://issues.apache.org/jira/browse/IGNITE-7176 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.3 >Reporter: Markus Kinzler > 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 (v6.4.14#64029)
