Return-Path: X-Original-To: apmail-atlas-dev-archive@minotaur.apache.org Delivered-To: apmail-atlas-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DC17B18EA5 for ; Sat, 19 Dec 2015 11:19:49 +0000 (UTC) Received: (qmail 31964 invoked by uid 500); 19 Dec 2015 11:19:49 -0000 Delivered-To: apmail-atlas-dev-archive@atlas.apache.org Received: (qmail 31919 invoked by uid 500); 19 Dec 2015 11:19:49 -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 31903 invoked by uid 99); 19 Dec 2015 11:19:49 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Dec 2015 11:19:49 +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 3F75B1805AE for ; Sat, 19 Dec 2015 11:19:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.226 X-Spam-Level: * X-Spam-Status: No, score=1.226 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.554] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ddNtmPDfqyL6 for ; Sat, 19 Dec 2015 11:19:48 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id AE91A21488 for ; Sat, 19 Dec 2015 11:19:47 +0000 (UTC) Received: (qmail 31896 invoked by uid 99); 19 Dec 2015 11:19:46 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Dec 2015 11:19:46 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A18262C0AFA for ; Sat, 19 Dec 2015 11:19:46 +0000 (UTC) Date: Sat, 19 Dec 2015 11:19:46 +0000 (UTC) From: "Hemanth Yamijala (JIRA)" To: dev@atlas.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ATLAS-405) UI: Lineage is broken seemingly if there are more than one input Processes creating a Dataset MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ATLAS-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hemanth Yamijala updated ATLAS-405: ----------------------------------- Attachment: failing_lineage.png working_lineage.png working_lineage -> Comes when I click on the first vertex in the graph. [DataSet 1] failing_lineage -> comes when I click on the central vertex in the first graph. [DataSet 2] > UI: Lineage is broken seemingly if there are more than one input Processes creating a Dataset > --------------------------------------------------------------------------------------------- > > Key: ATLAS-405 > URL: https://issues.apache.org/jira/browse/ATLAS-405 > Project: Atlas > Issue Type: Bug > Reporter: Hemanth Yamijala > Priority: Blocker > Attachments: failing_lineage.png, working_lineage.png > > > I have a slightly complex lineage which is like this: > [DataSet 1] -> (3 processes) -> [DataSet 2] -> (1 process) -> [DataSet 3] > When I click on DataSet1, the lineage graph is showing correctly. > When I click on DataSet2, the lineage graph is broken. What is happening is that there are 2 dangling processes on the input side of DataSet 2 which are not linked to the DataSet 1. Only one of the processes seems linked. It appears that maybe the graph walking is not taking into effect multiple inputs to a vertex like DataSet 2. > The API response is right. I will upload images of working and failing lineages with the corresponding responses in follow-up comments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)