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 6D746200C7C for ; Mon, 5 Jun 2017 15:03:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 6C4B3160BBF; Mon, 5 Jun 2017 13:03:09 +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 B0E3D160BD4 for ; Mon, 5 Jun 2017 15:03:08 +0200 (CEST) Received: (qmail 15590 invoked by uid 500); 5 Jun 2017 13:03:07 -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 15578 invoked by uid 99); 5 Jun 2017 13:03:07 -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; Mon, 05 Jun 2017 13:03:07 +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 5606B180533 for ; Mon, 5 Jun 2017 13:03:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, 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 ZU2awmzb7zUf for ; Mon, 5 Jun 2017 13:03:06 +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 8D59C5FE2F for ; Mon, 5 Jun 2017 13:03:05 +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 B7944E0BCA for ; Mon, 5 Jun 2017 13:03:04 +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 3CDFE21B58 for ; Mon, 5 Jun 2017 13:03:04 +0000 (UTC) Date: Mon, 5 Jun 2017 13:03:04 +0000 (UTC) From: "Keval Bhatt (JIRA)" To: dev@atlas.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Reopened] (ATLAS-1781) Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 05 Jun 2017 13:03:09 -0000 [ https://issues.apache.org/jira/browse/ATLAS-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reopened ATLAS-1781: -------------------------------- [~Xinzhi,Luo] I tested your patch it works good for 2 nodes. if we have more then 2 nodes it want render correctly. (i.e arrow color are not in correct order) To reproduce. * Run quick start. * Search for "Table". * Then go to "sales_fact" entity and check for Lineage. Please find attached screenshot. * wrong o/p -> after_test-wrong_op.png * expected - > expected.png > Atlas UI cannot show lineage pic when inputs and outputs of lineage are the same entity > --------------------------------------------------------------------------------------- > > Key: ATLAS-1781 > URL: https://issues.apache.org/jira/browse/ATLAS-1781 > Project: Atlas > Issue Type: Bug > Components: atlas-webui > Affects Versions: trunk, 0.7-incubating, 0.8-incubating, 0.7.1-incubating, 0.9-incubating > Reporter: qinglin,xia > Assignee: Xinzhi,Luo > Fix For: 0.9-incubating > > Attachments: 0001-fix-ATLAS-1781.patch, browser_error.png, fixed.png, Lineage_Create_Successfully_when_inputs_outputs_different.png, Lineage_keep_loading.png > > > I was working with the lineage for hbase, when I added a column family in a hbase table, I want to create a lineage for the table to show there is a change within the table schema, yet when I create a process using the atlas api, I found that the process entity is successfully created, but the lineage is not shown on the atlas web page. > Steps to Reproduce this issue is: > 1. build up an entity extends the DataSet Type > 2. build up a lineage Process > 3. set the process input and output to the same entity > The code is like: > Referenceable table1 = atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME, AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, input_table_name); > Referenceable table2 = atlasClient.getEntity(HBaseDataTypes.HBASE_TABLE_TYPE_NAME, AtlasClient.REFERENCEABLE_ATTRIBUTE_NAME, output_table_name); > HBaseProcess process = new HBaseProcess("process"); > process.setInput(table1.getId()); > process.setoutput(table2.getId()); > here I set the input_table_name and output_table_name the same string name, when I set them different values, the lineage pic can be shown for table1 and table2 successfully > Screenshots are: > 1) The lineage pic keep loading on the atlas UI > 2) The error log reported by the browser console > 3) The lineage pic showed successfully when set the inputs and outputs of the lineage to different entities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)