atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suma Shivaprasad (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1207) Dataset exists query in lineage APIs takes longer
Date Thu, 20 Oct 2016 19:17:58 GMT

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

Suma Shivaprasad commented on ATLAS-1207:
-----------------------------------------

+1

> Dataset exists query in lineage APIs takes longer
> -------------------------------------------------
>
>                 Key: ATLAS-1207
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1207
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Sharmadha Sainath
>            Assignee: Shwetha G S
>             Fix For: 0.8-incubating
>
>         Attachments: ATLAS-1207-v2.patch, ATLAS-1207.patch
>
>
> Hive_column now extends DataSet. Lineage Service uses the DSL query Dataset where __guid
= <id> which maps to the gremlin query g.V().has(supertype, Dataset).has(__guid, <id>).
Since the first filter is on type which returns many vertices, this query is slow. Supertypes
is a list property and not sure how adding combined index will work. This can be replaced
with graph query directly like 
> {code}
> titanGraph.query().has(Constants.GUID_PROPERTY_KEY, guid)
>                           .has(Constants.SUPER_TYPES_PROPERTY_KEY, AtlasClient.DATA_SET_SUPER_TYPE)
> {code}
> Thanks [~ssainath] for helping to test this



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

Mime
View raw message