You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maksim Zhuravkov (Jira)" <ji...@apache.org> on 2025/01/13 11:47:00 UTC
[jira] [Updated] (IGNITE-23947) Sql. Add a test to check operator signatures
[ https://issues.apache.org/jira/browse/IGNITE-23947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maksim Zhuravkov updated IGNITE-23947:
--------------------------------------
Description:
Apache Ignite 3 uses a lot of operators defined by calcite and it would be beneficial to have a snapshot of signatures of those operators to avoid bugs between calcite updates. To generate these signatures we can use SqlOperator::getAllowedSignatures
Proposed signatures file format:
{noformat}
F1(<numeric>)
F1(<string>)
#81a63101fa89dfb9b9115265fb519d7dda810aa2
F2(<string>) ***
F2() ***
#7f27a84679525580ba4fa549407c28de073c0f69
# - SHA-1 for an operator signature
*** - for custom signatures
{noformat}
Additionally, we can use this file to simplify a process of documenting of SQL functions of Apache Ignite 3.
was:
Apache Ignite 3 uses a lot of operators defined by calcite and it would be beneficial to have a snapshot of signatures of those operators to avoid bugs between calcite updates. To generate these signatures we can use SqlOperator::getAllowedSignatures
Proposed signatures file format:
{noformat}
F1(<numeric>)
F1(<string>)
#81a63101fa89dfb9b9115265fb519d7dda810aa2
F2(<string>) ***
F2() ***
#7f27a84679525580ba4fa549407c28de073c0f69
# - SHA-1 for an operator signature
*** - for custom signatures
{noformat}
> Sql. Add a test to check operator signatures
> --------------------------------------------
>
> Key: IGNITE-23947
> URL: https://issues.apache.org/jira/browse/IGNITE-23947
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Maksim Zhuravkov
> Assignee: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Apache Ignite 3 uses a lot of operators defined by calcite and it would be beneficial to have a snapshot of signatures of those operators to avoid bugs between calcite updates. To generate these signatures we can use SqlOperator::getAllowedSignatures
> Proposed signatures file format:
> {noformat}
> F1(<numeric>)
> F1(<string>)
> #81a63101fa89dfb9b9115265fb519d7dda810aa2
>
> F2(<string>) ***
> F2() ***
> #7f27a84679525580ba4fa549407c28de073c0f69
> # - SHA-1 for an operator signature
> *** - for custom signatures
> {noformat}
> Additionally, we can use this file to simplify a process of documenting of SQL functions of Apache Ignite 3.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)