[
https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14715992#comment-14715992
]
Julian Hyde commented on PHOENIX-953:
-------------------------------------
I was wrong. I checked SQL-2011, and you can specify more than one argument to
UNNEST, provided that they are all arrays. So you would not need to join the
arrays on ordinal.
7-6 table reference, syntax rule 7e case 1:
bq. If the declared type of any CVEj, 1 (one) ≤ j ≤ NCV, is a multiset, then
NCV shall be 1 (one) and WITH ORDINALITY shall not be specified.
> Support UNNEST for ARRAY
> ------------------------
>
> Key: PHOENIX-953
> URL: https://issues.apache.org/jira/browse/PHOENIX-953
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Dumindu Buddhika
> Fix For: 4.6
>
> Attachments: PHOENIX-953-v1.patch, PHOENIX-953-v2.patch,
> PHOENIX-953-v3.patch, PHOENIX-953-v4.patch
>
>
> The UNNEST built-in function converts an array into a set of rows. This is
> more than a built-in function, so should be considered an advanced project.
> For an example, see the following Postgres documentation:
> http://www.postgresql.org/docs/8.4/static/functions-array.html
> http://www.anicehumble.com/2011/07/postgresql-unnest-function-do-many.html
> http://tech.valgog.com/2010/05/merging-and-manipulating-arrays-in.html
> So the UNNEST is a way of converting an array to a flattened "table" which
> can then be filtered on, ordered, grouped, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
