You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Maryann Xue (JIRA)" <ji...@apache.org> on 2015/04/14 04:34:12 UTC

[jira] [Resolved] (PHOENIX-1842) Implement server sort and client sort logic in Phoenix/Calcite Integration

     [ https://issues.apache.org/jira/browse/PHOENIX-1842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maryann Xue resolved PHOENIX-1842.
----------------------------------
    Resolution: Fixed

> Implement server sort and client sort logic in Phoenix/Calcite Integration
> --------------------------------------------------------------------------
>
>                 Key: PHOENIX-1842
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1842
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Maryann Xue
>            Assignee: Maryann Xue
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> Implement PhoenixSort with ScanPlan or AggregatePlan or HashJoinPlan when possible; otherwise use ClientScanPlan or ClientAggregatePlan.
> Even if the sorting cannot be done over the server, as in a ScanPlan or in a ScanPlan wrapped by a HashJoinPlan, putting the sorting together with an AggregatePlan or an AggregatePlan wrapped by a HashJoinPlan would still be cheaper, since it would save an extra "spooling" process. We should make sure that is reflected in cost calculation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)