[
https://issues.apache.org/jira/browse/PHOENIX-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14009015#comment-14009015
]
James Taylor commented on PHOENIX-952:
--------------------------------------
One even simpler alternative would be to modify the grammar to recognize a
boolean expression with any ANY or ALL in it. In that case, you could generate
the ArrayAnyParseNode(lhs, ComparisonParseNode(ArrayIndexLoopParseNode(), rhs))
directly. I think the only other case is for IS NULL. In this case, no changes
would be required to ParseNodeRewriter and invalid usages of ANY/ALL would be
caught at parse time - you'd only need to verify that the lhs if of type ARRAY
in ExpressionCompiler then. I'd try this approach first.
> Support ANY and ALL built-ins for ARRAYs
> ----------------------------------------
>
> Key: PHOENIX-952
> URL: https://issues.apache.org/jira/browse/PHOENIX-952
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 3.0.0, 4.0.0
> Reporter: James Taylor
> Assignee: ramkrishna.s.vasudevan
> Fix For: 3.1, 4.1
>
> Attachments: Phoenix-932_1.patch, Phoenix-932_2.patch
>
>
> There's currently no good way to search array elements. We should support the
> ANY and ALL built-ins for our ARRAY type like Postgres does:
> http://www.postgresql.org/docs/9.1/static/arrays.html#ARRAYS-SEARCHING
--
This message was sent by Atlassian JIRA
(v6.2#6252)
