phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maryann Xue (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (PHOENIX-1842) Implement server sort and client sort logic in Phoenix/Calcite Integration
Date Tue, 14 Apr 2015 02:34:12 GMT

     [ 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)

Mime
View raw message