You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Chinmay Kulkarni (Jira)" <ji...@apache.org> on 2019/12/21 00:56:06 UTC
[jira] [Closed] (PHOENIX-4884) INSTR function should work
seamlessly with literal and non-literal arguments
[ https://issues.apache.org/jira/browse/PHOENIX-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chinmay Kulkarni closed PHOENIX-4884.
-------------------------------------
Bulk closing Jiras for the 4.15.0 release.
> INSTR function should work seamlessly with literal and non-literal arguments
> ----------------------------------------------------------------------------
>
> Key: PHOENIX-4884
> URL: https://issues.apache.org/jira/browse/PHOENIX-4884
> Project: Phoenix
> Issue Type: Bug
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Major
> Fix For: 4.15.0, 5.1.0
>
> Attachments: PHOENIX-4884.001.patch, PHOENIX-4884.002.patch, PHOENIX-4884.003.patch, PHOENIX-4884.004.patch
>
>
> INSTR's documentation reads as though it should support an expression or a literal for either argument. At least, it doesn't say that it only supports one or the other.
> However, the implementation only handles the case of {{INSTR(expr, literal)}}. We can pretty easily make this better and work with any combination:
> e.g. {{INSTR(literal, expr)}}, {{INSTR(expr, expr)}}, {{INSTR(literal, literal)}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)