[
https://issues.apache.org/jira/browse/IGNITE-23831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-23831:
--------------------------------------
Fix Version/s: 3.0
> Sql. ExecutionService must create unique executionId for retries for same
> queryId
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-23831
> URL: https://issues.apache.org/jira/browse/IGNITE-23831
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Konstantin Orlov
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Currently, execution service uses query id to uniquely identify cursor. The
> problem is, with introduced retries query may have more than a single cursor.
> And even though next attempt won't be started until current cursor is
> finalized locally, {{QueryCloseMessage}} stuck in an executor may close
> fragments created for next attempt.
> Execution service must differentiate cursors created for different attempts
> within the same query.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
