[jira] [Updated] (IGNITE-19504) Sql. Align difference between ignite and calcite runtime available functions.

2023-05-17 Thread Evgeny Stanilovsky (Jira)


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

Evgeny Stanilovsky updated IGNITE-19504:

Description: 
After [1] is done, we can proceed with functionality alignment.
IgniteSqlOperatorTable declare runtime available functions, thus undeclared 
functionality is not available for now, for example : 

{noformat}
select left('Chicago', 5)
{noformat}

will throw: NoSuchMethodException, the goal of this issue is functionality 
aligment for such of undeclared functions and append additional tests.

[1] https://issues.apache.org/jira/browse/IGNITE-19504


  was:
IgniteSqlOperatorTable declare runtime available functions, thus undeclared 
functionality is not available for now, for example : 

{noformat}
select left('Chicago', 5)
{noformat}

will throw: NoSuchMethodException, the goal of this issue is functionality 
aligment for such of undeclared functions and append additional tests.



> Sql. Align difference between ignite and calcite runtime available functions.
> -
>
> Key: IGNITE-19504
> URL: https://issues.apache.org/jira/browse/IGNITE-19504
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Evgeny Stanilovsky
>Priority: Major
>  Labels: calcite2-required, calcite3-required, ignite-3
>
> After [1] is done, we can proceed with functionality alignment.
> IgniteSqlOperatorTable declare runtime available functions, thus undeclared 
> functionality is not available for now, for example : 
> {noformat}
> select left('Chicago', 5)
> {noformat}
> will throw: NoSuchMethodException, the goal of this issue is functionality 
> aligment for such of undeclared functions and append additional tests.
> [1] https://issues.apache.org/jira/browse/IGNITE-19504



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


[jira] [Updated] (IGNITE-19504) Sql. Align difference between ignite and calcite runtime available functions.

2023-05-17 Thread Evgeny Stanilovsky (Jira)


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

Evgeny Stanilovsky updated IGNITE-19504:

Description: 
After [1] is done, we can proceed with functionality alignment.
IgniteSqlOperatorTable declare runtime available functions, thus undeclared 
functionality is not available for now, for example : 

{noformat}
select left('Chicago', 5)
{noformat}

will throw: NoSuchMethodException, the goal of this issue is functionality 
aligment for such of undeclared functions and append additional tests.

Need to register :
SqlLibraryOperators.ENDS_WITH
SqlLibraryOperators.STARTS_WITH

[1] https://issues.apache.org/jira/browse/IGNITE-19504


  was:
After [1] is done, we can proceed with functionality alignment.
IgniteSqlOperatorTable declare runtime available functions, thus undeclared 
functionality is not available for now, for example : 

{noformat}
select left('Chicago', 5)
{noformat}

will throw: NoSuchMethodException, the goal of this issue is functionality 
aligment for such of undeclared functions and append additional tests.

[1] https://issues.apache.org/jira/browse/IGNITE-19504



> Sql. Align difference between ignite and calcite runtime available functions.
> -
>
> Key: IGNITE-19504
> URL: https://issues.apache.org/jira/browse/IGNITE-19504
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Evgeny Stanilovsky
>Priority: Major
>  Labels: calcite2-required, calcite3-required, ignite-3
>
> After [1] is done, we can proceed with functionality alignment.
> IgniteSqlOperatorTable declare runtime available functions, thus undeclared 
> functionality is not available for now, for example : 
> {noformat}
> select left('Chicago', 5)
> {noformat}
> will throw: NoSuchMethodException, the goal of this issue is functionality 
> aligment for such of undeclared functions and append additional tests.
> Need to register :
> SqlLibraryOperators.ENDS_WITH
> SqlLibraryOperators.STARTS_WITH
> [1] https://issues.apache.org/jira/browse/IGNITE-19504



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


[jira] [Updated] (IGNITE-19504) Sql. Align difference between ignite and calcite runtime available functions.

2024-03-15 Thread Konstantin Orlov (Jira)


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

Konstantin Orlov updated IGNITE-19504:
--
Labels: calcite2-required ignite-3  (was: calcite2-required 
calcite3-required ignite-3)

> Sql. Align difference between ignite and calcite runtime available functions.
> -
>
> Key: IGNITE-19504
> URL: https://issues.apache.org/jira/browse/IGNITE-19504
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 3.0.0-beta1
>Reporter: Evgeny Stanilovsky
>Priority: Major
>  Labels: calcite2-required, ignite-3
>
> After [1] is done, we can proceed with functionality alignment.
> IgniteSqlOperatorTable declare runtime available functions, thus undeclared 
> functionality is not available for now, for example : 
> {noformat}
> select left('Chicago', 5)
> {noformat}
> will throw: NoSuchMethodException, the goal of this issue is functionality 
> aligment for such of undeclared functions and append additional tests.
> Need to register :
> SqlLibraryOperators.ENDS_WITH
> SqlLibraryOperators.STARTS_WITH
> [1] https://issues.apache.org/jira/browse/IGNITE-19504



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