phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-2090) Refine PhoenixTableScan.computeSelfCost() when scanRanges is available
Date Sat, 23 Jan 2016 21:56:39 GMT

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

Mime
View raw message