[
https://issues.apache.org/jira/browse/CALCITE-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16989487#comment-16989487
]
Rui Wang commented on CALCITE-3574:
-----------------------------------
I agree parser could pass directly without a change. Recently I have been
working on adding TUMBLE as a table-valued function. I did notice that Calcite
parser could parse an operator to SqlUnresolvedFunction, and later in
validation if it cannot find it by operator name from operator table, the query
will fail.
One potential benefit of adding "RLIKE" into parser is, if we think existing
POXIS_REGEXP is "RLIKE" in this Jira, we can code "RLIKE" in parser and let
parser directly create that operator. Validator uses name lookup to find
SqlUnresolvedFunction meaning it will less likely to let validator match
POXIS_REGEXP for you. However if we don't need reusing POXIS_REGEXP but create
a new "RLike" operator, parser change won't be necessary then.
> Add rlike syntax
> -----------------
>
> Key: CALCITE-3574
> URL: https://issues.apache.org/jira/browse/CALCITE-3574
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Aitozi
> Priority: Major
>
> Now rlike is not supported in calcite, i think it's useful to support this so
> that it can be used in other engine depending on calcite.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
