[
https://issues.apache.org/jira/browse/CALCITE-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084978#comment-17084978
]
Julian Hyde commented on CALCITE-3931:
--------------------------------------
Can you give an example of syntax that conflicts? I expect that you can create
a method that handles the first token and then dispatches to further methods.
Lookahead is expensive, so we should avoid it unless there is good
justification.
Lastly, I believe lookahead should be before the first item of a list, not
before every item.
> Add LOOKAHEAD(2) for methods defined in createStatementParserMethods
> --------------------------------------------------------------------
>
> Key: CALCITE-3931
> URL: https://issues.apache.org/jira/browse/CALCITE-3931
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.22.0
> Reporter: Danny Chen
> Assignee: Danny Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.23.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The default LOOKAHEAD is 1 which is very probably to conflict, especially for
> custom parse block like SqlCreate.
>
> Sets the LOOKAHEAD(2) to reduce conflict.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
