[
https://issues.apache.org/jira/browse/IGNITE-28651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18079117#comment-18079117
]
Dmitry Pavlov edited comment on IGNITE-28651 at 5/7/26 3:56 PM:
----------------------------------------------------------------
https://github.com/apache/ignite/commit/cb77103b3b27309821645e9d5cd0afe567a49c69
Cherry pick to
https://github.com/apache/ignite/commits/refs/heads/ignite-2.18/
Check
https://github.com/apache/ignite/actions/workflows/publish-website-on-branch-update.yml
Double check resulting UI:
https://ignite.apache.org/docs/ignite2/latest/SQL/sql-calcite#supported-functions
was (Author: dpavlov):
https://github.com/apache/ignite/commit/cb77103b3b27309821645e9d5cd0afe567a49c69
> Document Calcite SQL memory quotas in Ignite 2.x documentation
> --------------------------------------------------------------
>
> Key: IGNITE-28651
> URL: https://issues.apache.org/jira/browse/IGNITE-28651
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Reporter: Dmitry Pavlov
> Assignee: Dmitry Pavlov
> Priority: Minor
> Labels: ignite-2, ise
> Fix For: 2.18, 2.19
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ignite 2.x documentation should describe Calcite SQL memory quotas in a
> separate documentation task.
> The page should explain:
> * what memory the Calcite-based SQL engine accounts for;
> * global and per-query quota configuration;
> * how quotas protect the Java heap from large sorts, joins, aggregations, and
> result materialization;
> * how quota errors differ from JVM OutOfMemoryError;
> * how to monitor and size quotas for production queries;
> * how the page should be linked from SQL tuning and memory budget
> documentation.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
