[
https://issues.apache.org/jira/browse/IGNITE-27516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18062669#comment-18062669
]
Aleksandr commented on IGNITE-27516:
------------------------------------
merged
https://github.com/apache/ignite-3/commit/9707fe8742b301165e16159b15c7464259a63f1d
> CLI: Implement iterative cursor reading for SQL results
> -------------------------------------------------------
>
> Key: IGNITE-27516
> URL: https://issues.apache.org/jira/browse/IGNITE-27516
> Project: Ignite
> Issue Type: Improvement
> Reporter: Aleksandr
> Assignee: Aleksandr
> Priority: Major
> Labels: ignite-3
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Implement iterative (streaming) cursor reading for SQL query results in CLI
> to avoid loading entire result sets into memory.
> _Problem:_
> Currently, the CLI loads the entire query result into memory before
> displaying. For large result sets (millions of rows), this causes:
> * Out of memory errors
> * Long delays before any output appears
> * Poor user experience for large queries
> _Solution:_
> Read cursor data iteratively, displaying results in batches as they arrive.
> _New config keys:_
> * ignite.cli.sql.default-limit (integer, default: unlimited or 1000)
> * ignite.cli.sql.batch-size (integer, default: 100)
> _Requirements:_
> * Memory usage should be bounded regardless of result set size
> * First rows should appear quickly (low time-to-first-row)
> * Must integrate with pager (IGNITE-27514) - pager receives data incrementally
> * Show "... N more rows" indicator when limit applied
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
