Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 176EF200CE4 for ; Sun, 20 Aug 2017 13:04:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 15FB6164970; Sun, 20 Aug 2017 11:04:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5AEA016496D for ; Sun, 20 Aug 2017 13:04:05 +0200 (CEST) Received: (qmail 61298 invoked by uid 500); 20 Aug 2017 11:04:03 -0000 Mailing-List: contact dev-help@atlas.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@atlas.apache.org Delivered-To: mailing list dev@atlas.apache.org Received: (qmail 61286 invoked by uid 99); 20 Aug 2017 11:04:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Aug 2017 11:04:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id AF2B9180694 for ; Sun, 20 Aug 2017 11:04:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id L87331K7ITbo for ; Sun, 20 Aug 2017 11:04:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2C82F5F665 for ; Sun, 20 Aug 2017 11:04:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 53C3BE00A3 for ; Sun, 20 Aug 2017 11:04:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 086C621409 for ; Sun, 20 Aug 2017 11:04:00 +0000 (UTC) Date: Sun, 20 Aug 2017 11:04:00 +0000 (UTC) From: "David Radley (JIRA)" To: dev@atlas.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ATLAS-2070) Investigate why AtlasTypeRegistry caches elements without resolve references being run on them MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sun, 20 Aug 2017 11:04:06 -0000 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)