You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "David Radley (JIRA)" <ji...@apache.org> on 2017/08/20 11:04:00 UTC
[jira] [Created] (ATLAS-2070) Investigate why AtlasTypeRegistry
caches elements without resolve references being run on them
David Radley created ATLAS-2070:
-----------------------------------
Summary: Investigate why AtlasTypeRegistry caches elements without resolve references being run on them
Key: ATLAS-2070
URL: https://issues.apache.org/jira/browse/ATLAS-2070
Project: Atlas
Issue Type: Bug
Reporter: David Radley
During Jira 2029, I realised that AtlasTypeRegistry contains a map of the classificationTypes that did not have resolve references run on them. This means when a rest call to add a classificaiton to an entity comes in, AtlasEntityStoreV1 validateEntityAssociations calls AtlasClassificationType classificationType = typeRegistry.getClassificationTypeByName(newClassification);
This picks up the classificationType. Jira 2029 then resolves the references.
This Jira is to investigate whether the typeRegistry should store AtlasclassificationTypes with resolve references run on them. This would mean rewriting the junits.
Note constructing a classificationType passing a registry results in the resolve references being run. The other AtlasClassificationType constructor used by the junits and the typeregistry does not result in the resolve references being run.
If we can we should cache the resolve reference versions of the AtlasClassificationTypes - otehrwise callers of it get incomplete AltasClassificationTypes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)