[
https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael J. Carey updated ASTERIXDB-1779:
----------------------------------------
We've only done that so far for join orders - not for anything else -
and I'm thinking join orders are the only thing we should honor (in the
absence of cost info). For predicates, if we honor their order, we can't
use indexes....
> Processing the certain function predicates after a simple predicates
> --------------------------------------------------------------------
>
> Key: ASTERIXDB-1779
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1779
> Project: Apache AsterixDB
> Issue Type: Improvement
> Reporter: Taewoo Kim
> Assignee: Taewoo Kim
>
> For example, if we have the following AQL query,
> {code}
> for $i in dataset MyData
> where $i.id < 5 and edit-distance($i.name, "Arnold") < 2
> return $i;
> {code}
> It may be better to process *$i.id < 5* predicate first and then process
> *edit-distance($i.name, "Arnold")* predicate since the processing cost of the
> latter is higher than that of the former.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
