[
https://issues.apache.org/jira/browse/PHOENIX-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980030#comment-13980030
]
James Taylor commented on PHOENIX-136:
--------------------------------------
[~jhanit], [~damien.carol] - FYI we have derived table implemented in our
3.0,4.0, and master branch (including for joins with some restrictions).
Getting ready next week to release this as a 3.1/4.1 release (along with our
enhanced Pig Integration). Give a spin if you'd like a sneak peek.
> Support derived tables
> ----------------------
>
> Key: PHOENIX-136
> URL: https://issues.apache.org/jira/browse/PHOENIX-136
> Project: Phoenix
> Issue Type: Task
> Reporter: James Taylor
> Assignee: James Taylor
> Labels: enhancement
>
> Add support for derived queries of the form:
> SELECT * FROM ( SELECT company, revenue FROM Company ORDER BY revenue) LIMIT
> 10
> Adding support for this requires a compile time change as well as a runtime
> execution change. The first version of the compile-time change could limit
> aggregation to only be allowed in the inner or the outer query, but not both.
> In this case, the inner and outer queries can be combined into a single query
> with the outer select becoming just a remapping of a subset of the projection
> from the inner select. The second version of the compile-time change could
> handle aggregation in the inner and outer select by performing client side
> (this is likely a less common scenario).
> For the runtime execution, change the UngroupedAggregateRegionObserver would
> be modified to look for a new "TopNLimit" attribute with an int value in the
> Scan. This would control the maximum number of values for the coprocessor to
> hold on to as the scan is performed. Then the
> GroupedAggregatingResultIterator would be modified to handle keeping the topN
> values received back from all the child iterators.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
