[
https://issues.apache.org/jira/browse/PHOENIX-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008568#comment-14008568
]
James Taylor commented on PHOENIX-952:
--------------------------------------
I'd like to minimize the code changes for this. Let's assume ANY only makes
sense when used with a comparison expression (and only when used with an ARRAY
data type). We can flag any other usage as an error. In that case, treat the
ANY as an attribute that gets passed through to ComparisonParseNode and carried
into ComparisonExpression. The change should be isolated to these classes (and
classes that construct these). Then the runtime part is isolated in
ComparisonExpression - you do what occurs now, but you loop over all elements
instead of evaluating a single child element.
Make sense, [~ram_krish]?
> 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)
