[
https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849082#comment-15849082
]
Taewoo Kim commented on ASTERIXDB-1779:
---------------------------------------
[~tillw]: I just had a short conversation with [~dtabass] regarding your
comments. I still wonder if there is a strict reason that we need to keep the
original order of predicates (like the join branches: the first - outer, the
second - inner)? In other words, do we need to enforce the original order?
Mike's idea is that if we need to enforce the order, then we can provide a new
hint that enforces the original order. I still think that if that hint was not
specified, we can reorder the predicates to speed up the evaluation process.
> 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)
