Mailing-List: contact dev-help@atlas.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@atlas.incubator.apache.org
Date: Wed, 14 Jun 2017 14:04:00 +0000 (UTC)
From: "Christian R (JIRA)" <jira@apache.org>
To: dev@atlas.incubator.apache.org
Message-ID: <JIRA.13078575.1497003649000.17085.1497449040086@Atlassian.JIRA>
In-Reply-To: <JIRA.13078575.1497003649000@Atlassian.JIRA>
References: <JIRA.13078575.1497003649000@Atlassian.JIRA> <JIRA.13078575.1497003649138@jira-lw-us.apache.org>
Subject: [jira] [Commented] (ATLAS-1868) Highly inefficient DSL-queries
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 14 Jun 2017 14:04:08 -0000


    [ https://issues.apache.org/jira/browse/ATLAS-1868?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1604=
9209#comment-16049209 ]=20

Christian R commented on ATLAS-1868:
------------------------------------

Hi Graham,=20

thank you for looking into this and I am glad you are able to reproduce it.=
=20

The only think I have thought of so far is to leverage the solr/elastic ind=
ex to see if we can detect parts of the graph that have very few entries an=
d base the query around that. I suspect not, but it was my first thought (i=
 used to work with search, you see...)

(I want to sneak in a question here that I couldn't find any discussion on;=
 was it a deliberate choice to remove the titan id from gremlin search resu=
lts in v 0.8 and above? I get out/inVertex in the edge results, but the ver=
tices no longer contain 'id'. At least, not when running on berkeley/elasti=
c locally. I am trying to verify on hdp sandbox 2.6 now. Given my perf issu=
es with DSL we are using gremlin quite heavily on v 0.7 now. )

> Highly inefficient DSL-queries
> ------------------------------
>
>                 Key: ATLAS-1868
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1868
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 0.7-incubating
>         Environment: linux, hbase + solr configuration.
>            Reporter: Christian R
>              Labels: dsl, gremlin
>
> The DSL query 'mytype where property.id =3D "id1"' appears to be rewritte=
n as a gremlin query that resembles:
> g.V.has(typename, 'mytype'=C2=A8).as(x).out('property').has('id', 'id1').=
back('x')
> On our system this query takes 6-7 minutes. The query
> g.V.has('id', 'id1').in('property').has('typename', 'mytype')
> takes 350 milliseconds.
> Our graph:
> g.V.count() =3D 1359151
> We have atlas 0.7 installed. I've compiled the latest 0.9 code and looked=
 at the generated gremlin query as reported in the logs for the same DSL-qu=
ery, and I think 0.9 has the same performance issues. Unfortunately I don't=
 have a big graph on a 0.9 installation to test performance.=20


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)