[
https://issues.apache.org/jira/browse/ATLAS-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394996#comment-15394996
]
Suma Shivaprasad edited comment on ATLAS-1060 at 7/27/16 3:25 AM:
------------------------------------------------------------------
The other choice is to enable composite indexes for all attributes. Have
attached patch ATLAS-1060-all-attributes.patch with this approach. Based on
perf impact and numbers, could decide on which option to choose. But
inituitively , enabling for all attributes would definitely increase write
latency for entities and hence we need to evaluate this carefully.
was (Author: suma.shivaprasad):
The other choice is to enable composite indexes for all attributes. Have
attached patch ATLAS-1060-all-attributes.patch with this approach. Based on
perf impact and numbers, could decide on which option to choose.
> Add composite indexes for exact match performance improvements for
> selected/all attributes
> ------------------------------------------------------------------------------------------
>
> Key: ATLAS-1060
> URL: https://issues.apache.org/jira/browse/ATLAS-1060
> Project: Atlas
> Issue Type: Bug
> Affects Versions: 0.7-incubating, 0.8-incubating
> Reporter: Suma Shivaprasad
> Assignee: Suma Shivaprasad
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1060-all-attributes.patch, ATLAS-1060.patch
>
>
> Proposal is to add a flag for each attribute which is by default 'false' for
> creating exact match indexes (titan composite indexes). By default mixed
> idexes are created but not used for exact matches. The proposal is to add
> them for selected attributes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
