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/11/06 03:10:27 UTC

[jira] [Updated] (PHOENIX-2089) Use index when skip-scan is possible or when ordering key matches

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

Maryann Xue updated PHOENIX-2089:
---------------------------------
    Labels: calcite  (was: )

> Use index when skip-scan is possible or when ordering key matches
> -----------------------------------------------------------------
>
>                 Key: PHOENIX-2089
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2089
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Maryann Xue
>            Assignee: Maryann Xue
>              Labels: calcite
>   Original Estimate: 240h
>  Remaining Estimate: 240h
>
> This is very basic work for secondary index and depends on the fix for CALCITE-761 and CALCITE-763.
> Further work should be done in PhoenixTableScan.computeSelfCost() to give a more accurate estimate for better matching among different indices.



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