You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitry Pavlov (Jira)" <ji...@apache.org> on 2022/09/27 17:07:00 UTC
[jira] [Updated] (IGNITE-15128) Calcite: Take own control of SQL functions
[ https://issues.apache.org/jira/browse/IGNITE-15128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitry Pavlov updated IGNITE-15128:
-----------------------------------
Summary: Calcite: Take own control of SQL functions (was: Take own control of SQL functions)
> Calcite: Take own control of SQL functions
> ------------------------------------------
>
> Key: IGNITE-15128
> URL: https://issues.apache.org/jira/browse/IGNITE-15128
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Assignee: Aleksey Plekhanov
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> As of now, we use a set of 4 database function dialects:
> SqlLibrary.STANDARD,
> SqlLibrary.POSTGRESQL,
> SqlLibrary.ORACLE,
> SqlLibrary.MYSQL
> Seems we should have owned our dialect with a subset of the aforementioned functions and have the ability to modify already exists functions and add a new one.
> During implementation need to sort out similar functions and choose just one of them to avoid duplication,
> See :
> org.apache.calcite.util.BuiltInMethod
> org.apache.calcite.sql.fun.SqlLibraryOperators
> org.apache.calcite.runtime.SqlFunctions
> org.apache.ignite.internal.processors.query.calcite.exec.exp.RexImpTable
--
This message was sent by Atlassian Jira
(v8.20.10#820010)