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

Posted to dev@atlas.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2019/06/27 14:13:00 UTC

[jira] [Updated] (ATLAS-1208) DSL query optimisation

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

Madhan Neethiraj updated ATLAS-1208:
------------------------------------
    Fix Version/s:     (was: 0.8-incubating)

> DSL query optimisation
> ----------------------
>
>                 Key: ATLAS-1208
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1208
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Sharmadha Sainath
>            Priority: Major
>
> DSL queries always have the type. The DSL query is transformed into gremlin of the form: {{g.V().has(type, <type>).has(name, <name>)}}. This is not efficient as the first has clause returns many vertices. Instead, if we generate the gremlin query as {{g.V().has(name, <name>).has(type, <type>)}}, the query should execute faster as the first predicate will filter more vertices



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)