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

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/01/23 22:56:39 UTC

[jira] [Updated] (PHOENIX-2090) Refine PhoenixTableScan.computeSelfCost() when scanRanges is available

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

James Taylor updated PHOENIX-2090:
----------------------------------
    Assignee: Maryann Xue

> Refine PhoenixTableScan.computeSelfCost() when scanRanges is available
> ----------------------------------------------------------------------
>
>                 Key: PHOENIX-2090
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2090
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Maryann Xue
>            Assignee: Maryann Xue
>              Labels: calcite
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> We should compute a more accurate cost based on the "scanRanges" so that we can better choose among these different indices.
> For example, if we have more than one indices concerning different index keys, for example IDX1 is indexed on column a, and IDX2 is indexed on column b, and our query is like "select x, y, z where a between 'A1' and 'A2' and b between 'B3' and 'B4'.



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