[
https://issues.apache.org/jira/browse/IGNITE-18674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17694641#comment-17694641
]
Aleksandr commented on IGNITE-18674:
------------------------------------
I've introduced the core functionality for background async calls with a
progress bar. The SQL completion hanging is fixed with background async
initialization.
I don't see any reason to use a UI thread with a special API.
> Introduce UI thread to CLI
> --------------------------
>
> Key: IGNITE-18674
> URL: https://issues.apache.org/jira/browse/IGNITE-18674
> Project: Ignite
> Issue Type: Task
> Components: cli
> Reporter: Aleksandr
> Assignee: Aleksandr
> Priority: Major
> Labels: ignite-3
>
> The current SQL query completion process may obstruct the UI thread and
> result in CLI hang-ups when Ignite 3 node fails to respond.
> To prevent this issue, we need to implement a separate UI thread for all
> user-facing operations with a maximum block time of 5-10 seconds. The CLI
> must be protected from indefinite hang-ups at all times, regardless of Ignite
> 3 node behavior. To accomplish this, we should adopt a single UI thread and
> worker pool design with asynchronous communication, allowing the UI thread to
> receive notifications without being blocked.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
