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

Posted to notifications@asterixdb.apache.org by "Wenhai (JIRA)" <ji...@apache.org> on 2016/02/14 08:24:18 UTC

[jira] [Comment Edited] (ASTERIXDB-772) Optimizer should always pick Indexed NL Join over FuzzyJoin when index is available

    [ https://issues.apache.org/jira/browse/ASTERIXDB-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15146424#comment-15146424 ] 

Wenhai edited comment on ASTERIXDB-772 at 2/14/16 7:23 AM:
-----------------------------------------------------------

We can only choose one strategy to enforce the optimization for string based fuzzy join, i.e. either on inverted index or prefix based pruning join. Current status buyes the idea of the later, but we can try to switch the both based on the cardinarlity estimation once the fuzzy join operator is coupled with a select clause on a same join operand.


was (Author: lwhay):
We can only choose one strategy to enforce the optimization for string based fuzzy join, i.e. either on inverted index or prefix based pruning join. Current status buyes the idea of the later, but we can try to switch the both based on the cardinarlity estimation once the fuzzy join operator is coupled with a select clause on a same join opera.

> Optimizer should always pick Indexed NL Join over FuzzyJoin when index is available
> -----------------------------------------------------------------------------------
>
>                 Key: ASTERIXDB-772
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-772
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: AsterixDB, Similarity
>            Reporter: asterixdb-importer
>            Assignee: Wenhai
>            Priority: Minor
>              Labels: FixedInBranch
>
> Optimizer should always pick Indexed NL Join over FuzzyJoin when index is available



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