You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Loknath Priyatham Teja Singamsetty (JIRA)" <ji...@apache.org> on 2016/08/29 08:08:20 UTC
[jira] [Commented] (PHOENIX-3215) Add oracle regexp_like function
in phoenix
[ https://issues.apache.org/jira/browse/PHOENIX-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15445188#comment-15445188 ]
Loknath Priyatham Teja Singamsetty commented on PHOENIX-3215:
--------------------------------------------------------------
From [~larsh],
Regex' have the potential to be extremely slow and CPU intensive. We need to be careful if we're allowing this at scale.
> Add oracle regexp_like function in phoenix
> ------------------------------------------
>
> Key: PHOENIX-3215
> URL: https://issues.apache.org/jira/browse/PHOENIX-3215
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Loknath Priyatham Teja Singamsetty
> Assignee: Loknath Priyatham Teja Singamsetty
> Priority: Minor
>
> We have regexp_substr today which returns a substring of a string by applying a regular expression start from the offset of a one-based position.
> However, when using query builder frameworks like JOOQ code generators that generates java code from database and build type safe sql queries out of box, lack of regexp_like syntax is making developers to take work arounds to build the equivalent queries.
> Hard coding Query for regexp_substr as JOOQ does not support it:
> {quote}
> regex = regex + " AND regexp_substr("+ TestResultEntity.Column.BASELINE_MESSAGE.getName() +", ?)" + matching;
> {quote}
> Here is the oracle documentation for regexp_like https://docs.oracle.com/cd/B12037_01/server.101/b10759/conditions018.htm
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)