[
https://issues.apache.org/jira/browse/CALCITE-5118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17529687#comment-17529687
]
Julian Hyde commented on CALCITE-5118:
--------------------------------------
When CALCITE-1606 created {{class SqlDataPartFunction}} by renaming {{classÂ
SqlQuarterFunction}}, it added the {{rewriteCall}} method and removed code from
{{StandardConvertletTable}}. I believe that this issue would not exist if the
logic had remained in {{StandardConvertletTable}}.
Restoring that logic is one option; another option is to change
{{rewriteCall}}. I don't have a strong preference, as long as the validation
unit tests I described above work correctly.
> SqlDatePartFunction#rewriteCall should check operands length
> ------------------------------------------------------------
>
> Key: CALCITE-5118
> URL: https://issues.apache.org/jira/browse/CALCITE-5118
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.30.0
> Reporter: Benchao Li
> Assignee: Benchao Li
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.31.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> {{SqlDatePartFunction#rewriteCall}} does not check operands length for now,
> and it will be rewrite to {{EXTRACT}} unconditionally before validation.
> E.g.
> {code:sql}
> select week(); -- will throw ArrayIndexOutOfBoundsException
> select week(date '2022-04-27', 1); -- will just ignore second param
> {code}
> However, these cases should throw validation exceptions, because {{week}}
> actually only accept 1 operand.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
