You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Madhan Neethiraj (JIRA)" <ji...@apache.org> on 2018/05/17 05:43:00 UTC
[jira] [Updated] (ATLAS-1527) Batch entity retrievals in
DefaultMetadataService.loadEntities
[ https://issues.apache.org/jira/browse/ATLAS-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Madhan Neethiraj updated ATLAS-1527:
------------------------------------
Fix Version/s: 0.8-incubating
Component/s: atlas-core
Committed to master: http://git-wip-us.apache.org/repos/asf/atlas/commit/1e105174
> Batch entity retrievals in DefaultMetadataService.loadEntities
> --------------------------------------------------------------
>
> Key: ATLAS-1527
> URL: https://issues.apache.org/jira/browse/ATLAS-1527
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Reporter: Wojciech Wojcik
> Assignee: Wojciech Wojcik
> Priority: Minor
> Fix For: 0.8-incubating
>
> Attachments: rb56324.patch
>
>
> DefaultMetadataService.loadEntities() is called at the conclusion of entity creation and update, to load the created/updated entities which are passed to the EntityChangeListener's. The entities are being loaded one at time, because MetadataRepository does not expose a method to retrieve multiple entities by GUID. MetadataRepository can be enhanced to provide a getEntityDefinitions() entrypoint, and the implementation in GraphBackedMetadataRepository can batch the vertex retrievals using GraphHelper.getVerticesForGUIDs(). This will reduce the graph calls to retrieve the vertices.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)