[
https://issues.apache.org/jira/browse/CALCITE-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756541#comment-17756541
]
LakeShen commented on CALCITE-5937:
-----------------------------------
Hi [~jiajunbernoulli] ,Sorry for misunderstanding your question.
Normally, if the user declares the contents of the Hint, there should be a
Hint. But we could't control how the user uses it, and my idea is that even
without Hint, it shouldn't affect SQL execution.
Thanks for your suggestion, I will change the title of JIRA and PR.
> The parsing error should not be thrown even if there is empty Hint
> ------------------------------------------------------------------
>
> 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)
