[
https://issues.apache.org/jira/browse/PHOENIX-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14000557#comment-14000557
]
James Taylor commented on PHOENIX-952:
--------------------------------------
Good point, [~ram_krish]. I think the actual execution/runtime part of this can
likely become part of the ComparisonExpression. We'll just need to thread
through a new ANY/ALL enum.
The parsing is independent of what it gets compiled into. We can use ANY/ALL in
the grammar, and check for this either
- in ParseNodeRewriter.visitLeave(ComparisonParseNode) where we could generate
a new ComparisonParseNode with a new enum of ANY or ALL. This information would
get passed through to the ComparisonExpression that gets generated, or
- in ComparisonExpression.create() we could check if the child is an ANY or ALL
expression and pass through extra in the ComparisonExpression that gets
generated.
What are the restrictions around where an ANY versus ALL may be used? Is it
only allowed in a comparison expression?
> 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
> Fix For: 3.1, 4.1
>
> Attachments: Phoenix-932_1.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)
