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 F2944200B35 for ; Tue, 21 Jun 2016 00:57:06 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id F1730160A66; Mon, 20 Jun 2016 22:57: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 4BF73160A55 for ; Tue, 21 Jun 2016 00:57:06 +0200 (CEST) Received: (qmail 92687 invoked by uid 500); 20 Jun 2016 22:57:05 -0000 Mailing-List: contact dev-help@atlas.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@atlas.incubator.apache.org Delivered-To: mailing list dev@atlas.incubator.apache.org Received: (qmail 92676 invoked by uid 99); 20 Jun 2016 22:57:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jun 2016 22:57:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 1048EC1729 for ; Mon, 20 Jun 2016 22:57:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -5.446 X-Spam-Level: X-Spam-Status: No, score=-5.446 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id HCtxJSXtcbKL for ; Mon, 20 Jun 2016 22:57:04 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id EB5FF5F1F7 for ; Mon, 20 Jun 2016 22:57:03 +0000 (UTC) Received: (qmail 91703 invoked by uid 99); 20 Jun 2016 22:56:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jun 2016 22:56:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 0C9642C0451 for ; Mon, 20 Jun 2016 22:56:58 +0000 (UTC) Date: Mon, 20 Jun 2016 22:56:58 +0000 (UTC) From: "Suma Shivaprasad (JIRA)" To: dev@atlas.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ATLAS-919) UI : Deleted references should be filtered out MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 20 Jun 2016 22:57:07 -0000 [ https://issues.apache.org/jira/browse/ATLAS-919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suma Shivaprasad updated ATLAS-919: ----------------------------------- Description: Foe eg: In a hive_table one of the columns could be dropped in which case the columns array will have the deleted column as well. This could be completely filtered out in the UI. The way to identify this is to check if the entity state is DELETED when going through the references. (was: Foe eg: In a hive_table one of the columns could be dropped in which case the columns array will have the deleted column as well. This could be completely filtered out in the UI. the way to identify this is to check if the entity status is DELETED when going through the references.) > UI : Deleted references should be filtered out > ---------------------------------------------- > > Key: ATLAS-919 > URL: https://issues.apache.org/jira/browse/ATLAS-919 > Project: Atlas > Issue Type: Bug > Affects Versions: 0.7-incubating > Reporter: Suma Shivaprasad > Assignee: Keval Bhatt > Priority: Critical > Fix For: 0.7-incubating > > Attachments: 91529261-d568-40ee-9b2e-b488cff61de1.json > > > Foe eg: In a hive_table one of the columns could be dropped in which case the columns array will have the deleted column as well. This could be completely filtered out in the UI. The way to identify this is to check if the entity state is DELETED when going through the references. -- This message was sent by Atlassian JIRA (v6.3.4#6332)