[ 
https://issues.apache.org/jira/browse/CALCITE-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824226#comment-17824226
 ] 

 EveyWu edited comment on CALCITE-6278 at 3/7/24 2:39 AM:
----------------------------------------------------------

# Fixed summary symbol issue
 # Sure, in spark, RLIKE has the same semantics as REGEXP_LIKE and REGEXP,  and 
has been combined in the test.
 # Judging by the engine execution behavior, Hive also performs the unescape.
 # Add more unescape tests  in `SqlOperatorTest`

!image-2024-03-07-09-32-27-002.png|width=426,height=392!


was (Author: eveywu):
# Fixed summary symbol issue
 # Sure, in spark, RLIKE has the same semantics as REGEXP_LIKE and REGEXP,  and 
has been combined in the test.
 # Judging by the engine execution behavior, Hive also performs the unescape.

!image-2024-03-07-09-32-27-002.png|width=426,height=392!

> Add REGEXP, REGEXP_LIKE  function (enabled in Spark library)
> ------------------------------------------------------------
>
>                 Key: CALCITE-6278
>                 URL: https://issues.apache.org/jira/browse/CALCITE-6278
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter:  EveyWu
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.37.0
>
>         Attachments: image-2024-03-07-09-32-27-002.png
>
>
> Add Spark functions that have been implemented but have different 
> OperandTypes/Returns.
> Add Function 
> [REGEXP|https://spark.apache.org/docs/latest/api/sql/index.html#regexp], 
> [REGEXP_LIKE|https://spark.apache.org/docs/latest/api/sql/index.html#regexp_like]
>  # Since this function has the same implementation as the Spark 
> [RLIKE|https://spark.apache.org/docs/latest/api/sql/index.html#rlike] 
> function, the implementation can be directly reused.
>  # Since Spark 2.0, string literals (including regex patterns) are unescaped 
> in SQL parser, also fix this bug in calcite.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to