You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Suma Shivaprasad (JIRA)" <ji...@apache.org> on 2017/01/10 19:25:58 UTC

[jira] [Commented] (ATLAS-1404) Improve lineage performance with query filters using only GUID

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

Suma Shivaprasad commented on ATLAS-1404:
-----------------------------------------

Pushed to 0.7-incubating at https://github.com/apache/incubator-atlas/commit/3407303d7876ec8a90539c4d6737607116439989#diff-ebb5d6558caa36a18c3bb7e59711ac38

> Improve lineage performance with query filters using only GUID
> --------------------------------------------------------------
>
>                 Key: ATLAS-1404
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1404
>             Project: Atlas
>          Issue Type: Improvement
>    Affects Versions: 0.8-incubating
>            Reporter: Suma Shivaprasad
>            Assignee: Suma Shivaprasad
>             Fix For: 0.8-incubating, 0.7.1-incubating
>
>         Attachments: ATLAS-1404.1.patch, ATLAS-1404.patch
>
>
> Linage currently queries by superTypeName + guid combinations for which a composite index does not exist and index exists for typeName or guid alone. Subsequent filters are getting applied on typename query results which take a long time to finish. Hence rewriting these queries to use the GUID alone for querying and then apply the supertype checks once the entity definition is retrieved from the repository using its type



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