You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2026/09/01 10:29:00 UTC

[jira] [Updated] (IGNITE-29015) SQL Calcite: Provide a unified mechanism for fine-grained SQL semantics customization

     [ https://issues.apache.org/jira/browse/IGNITE-29015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vyacheslav Koptilin updated IGNITE-29015:
-----------------------------------------
    Fix Version/s: 2.19

> SQL Calcite: Provide a unified mechanism for fine-grained SQL semantics customization
> -------------------------------------------------------------------------------------
>
>                 Key: IGNITE-29015
>                 URL: https://issues.apache.org/jira/browse/IGNITE-29015
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Kirill Tkalenko
>            Assignee: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-2
>             Fix For: 2.19
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Calcite may require fine-grained settings that affect SQL validation, planning, and execution. Currently, *{{IgniteSqlPaginationPolicy}}* is an example of such a setting.
> Adding more independent policies may complicate their propagation through the query pipeline.
> Consider introducing an immutable *{{IgniteSqlSemantics}}* object that:
>  * contains fine-grained SQL settings;
>  * is passed through Calcite {*}{{Context}}{*};
>  * can be provided by a plugin through {*}{{FrameworkConfig}}{*};
>  * has default values preserving existing behavior.
> Initially, it can contain the pagination rounding mode. Later, it can support other settings, such as Oracle-compatible handling of {{''}} as {{{}NULL{}}}.
> The initial change should not introduce public configuration or change existing SQL behavior.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)