atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ATLAS-1042) Performance improvement changes for propertykey+typeName based queries
Date Fri, 22 Jul 2016 07:12:20 GMT

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

Shwetha G S resolved ATLAS-1042.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 0.8-incubating

Committed to master. Thanks Suma

> Performance improvement changes for propertykey+typeName based queries
> ----------------------------------------------------------------------
>
>                 Key: ATLAS-1042
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1042
>             Project: Atlas
>          Issue Type: Bug
>            Reporter: Suma Shivaprasad
>            Assignee: Suma Shivaprasad
>             Fix For: 0.8-incubating
>
>         Attachments: ATLAS-1042.patch
>
>
> The current entity writes which run with qualifiedName + typeName + state seem to be
running slow since composite indexes do not exist for qualifiedName+typeName which seems to
explain the regression caused in ATLAS-911 which added typeName for unique checks. 
> This jira is to address that and possibly explore any other optimizations that could
be done for propertyKey+typeName based queries like name+typeName which are pretty common



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

Mime
View raw message