[ https://issues.apache.org/jira/browse/CALCITE-6278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17824226#comment-17824226 ]
EveyWu commented on CALCITE-6278: ---------------------------------- # 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. ``` 0: jdbc:hive2://127.0.0.1:10000> select 'abc' RLIKE '^\abc$'; +-------+ | _c0 | +-------+ | true | +-------+ 0: jdbc:hive2://127.0.0.1:10000> select '\abc' RLIKE '^abc$'; +-------+ | _c0 | +-------+ | true | +-------+ ``` > 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 > > > 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)