You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2026/01/21 07:43:00 UTC
[jira] [Assigned] (IGNITE-27609) [SQL] PlannerHelper sometimes may fail with NoSuchElementException
[ https://issues.apache.org/jira/browse/IGNITE-27609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Orlov reassigned IGNITE-27609:
-----------------------------------------
Assignee: Konstantin Orlov
> [SQL] PlannerHelper sometimes may fail with NoSuchElementException
> ------------------------------------------------------------------
>
> Key: IGNITE-27609
> URL: https://issues.apache.org/jira/browse/IGNITE-27609
> Project: Ignite
> Issue Type: Bug
> Components: sql ai3
> Affects Versions: 3.2
> Reporter: Andrey Khitrin
> Assignee: Konstantin Orlov
> Priority: Critical
> Labels: ignite-3
>
> Since 2026-01-15, our automated tests have started to periodically find consistency issues with transactional access over JDBC. I'm currently working on a simple reproducer, but the general approach for reproduction is the following:
> # Use JDBC (I'm not sure if thin client is affected or not);
> # Use transactions;
> # Read/update the same table from several threads;
> # Check consistency of updated table after some time.
> Currently, there are at least two complex tests that periodically (~10% of time) fail on newer (after Jan 15) AI3 builds. Therefore, I consider that some breaking change may have had place slightly before that (somewhere around Jan 13-14, maybe). More information will be added.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)