[
https://issues.apache.org/jira/browse/CALCITE-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756454#comment-17756454
]
Jiajun Xie commented on CALCITE-5937:
-------------------------------------
[~shenlang], You didn't answer my question.
I think JIRA title can be better.
The parsing error should not be thrown even if there is *empty* Hint.
> The parsing error should not be thrown even if there is no Hint in Hint
> Statement
> ---------------------------------------------------------------------------------
>
> Key: CALCITE-5937
> URL: https://issues.apache.org/jira/browse/CALCITE-5937
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: LakeShen
> Assignee: LakeShen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.36.0
>
> Attachments: image-2023-08-18-17-43-30-254.png,
> image-2023-08-19-21-01-52-505.png
>
>
> Hints are a special kind of SQL comment,so even if there is no Hint in Hint
> Statement,it should not throw the sql parser error.
> Now in the calcite,for the following sql query, it would throw an SQL parsing
> error:
> {code:java}
> select /*+ */ deptno, min(foo) as x from emp {code}
> The exception is :
> !image-2023-08-18-17-43-30-254.png|width=615,height=298!
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
