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/16 04:26:58 UTC

[jira] [Updated] (PHOENIX-1859) Implement PhoenixLimit in Phoenix/Calcite Integration

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

Maryann Xue updated PHOENIX-1859:
---------------------------------
    Summary: Implement PhoenixLimit in Phoenix/Calcite Integration  (was: Implement PhoenixLimit with server-side and client-side conventions in Phoenix/Calcite Integration)

> Implement PhoenixLimit in Phoenix/Calcite Integration
> -----------------------------------------------------
>
>                 Key: PHOENIX-1859
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1859
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Maryann Xue
>            Assignee: Maryann Xue
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Limit is represented as a Sort RelNode in Calcite. We will do sort and limit together if sort spec is present (see PHOENIX-1858). Otherwise we will have a standalone PhoenixLimit, for which more aggressive optimization rules can be applied than for PhoenixSort.



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