atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apoorv Naik (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1388) Cache entities that are created/updated
Date Fri, 16 Dec 2016 03:01:07 GMT

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

Apoorv Naik commented on ATLAS-1388:
------------------------------------

[~dkantor] Could you take a look at the new v2 APIs ? There's something called a TypeRegistry
that does the in-memory caching (can be extended if needed). The goal is to make use of the
V2 APIs are they're more structured and have a well defined REST interface than the existing
TypeResource and EntityResource.

> Cache entities that are created/updated
> ---------------------------------------
>
>                 Key: ATLAS-1388
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1388
>             Project: Atlas
>          Issue Type: Improvement
>            Reporter: David Kantor
>            Assignee: Jeffrey Hagelberg
>
> - Cache created entities in RequestContext when they are created.
> - Update/refactor DefaultMetadataService.loadEntities() to use the cached created entities.
> - Use the cache in the following places:
> ** FullTextMapper
> ** DefaultMetadataService.onEntitiesAdded - check cache before calling DefaultMetadataService.loadEntities
> ** DefaultMetadataService.onEntitiesUpdated - check cache before calling DefaultMetadataService.loadEntities

> ** EntityResource.getEntityDefinition - check cache before calling DefaultMetadataService.getEntityDefinition
> ** EntityResource.getResponse - check cache before calling DefaultMetadataService.getEntityDefinition



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

Mime
View raw message