[
https://issues.apache.org/jira/browse/IGNITE-28999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18106425#comment-18106425
]
Ignite TC Bot commented on IGNITE-28999:
----------------------------------------
{panel:title=Branch: [pull/13496/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13496/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Calcite SQL 1{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=9297600]]
* {color:#013220}IgniteCalciteTestSuite:
ParserCodegenResourcesTest.testParserCodegenResourcesAvailable - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9297715&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9297715
rerunBuildIds=9298050{color}
> SQL Calcite: Plugable SQL grama
> -------------------------------
>
> Key: IGNITE-28999
> URL: https://issues.apache.org/jira/browse/IGNITE-28999
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: calcite, ignite-2, sql
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3.Motivation
> SQL syntax varies across database systems. In some cases, Ignite needs to
> support non-ANSI SQL syntax or database-specific extensions.
> Apache Calcite allows a custom SQL parser to be generated from an extended
> grammar. A similar approach can be used in Ignite so that plugins can
> introduce additional SQL statements or clauses while retaining the standard
> Calcite syntax and all Ignite-specific SQL extensions.
> h3.Implementation Notes
> Add the ability for an Ignite plugin to provide a custom SQL parser.
> The Ignite-specific grammar files (`config.fmpp` and `parserImpls.ftl`) must
> be included as resources in the `ignite-calcite` artifact. A plugin can
> combine these resources with the base Calcite grammar, Ignite grammar, and
> its own grammar extensions to generate a custom parser at build time.
> The generated parser can then be registered through the plugin-provided
> Calcite `FrameworkConfig`.
> h3.Definition of Done
> * Plugins can extend the Ignite SQL grammar with additional statements or
> clauses.
> * A plugin-generated parser retains the standard Calcite and Ignite-specific
> SQL syntax.
> * The default Ignite SQL parser remains unchanged when no grammar plugin is
> installed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
