[
https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14695612#comment-14695612
]
James Taylor commented on PHOENIX-953:
--------------------------------------
Sorry for all the back-and-forth, [~Dumindux]. I think a good path for you to
take will be:
- Implement some tests with some simple table schemas using the standard SQL
UNNEST syntax (see Julian's comment above). Run these tests against a database
that supports standard UNNEST - maybe Apache Derby or Apache Drill? Or Oracle
as a last resort.
- Implement the runtime component for it wrt to ARRAYs as we've described above.
- [~maryannxue] will plug this into our Phoenix calcite branch and we'll target
this feature for when we release on top of Calcite.
> 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
> Attachments: PHOENIX-953-v1.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)
