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 7EDF718C2D for ; Fri, 23 Oct 2015 14:52:30 +0000 (UTC) Received: (qmail 72910 invoked by uid 500); 23 Oct 2015 14:52:30 -0000 Delivered-To: apmail-atlas-dev-archive@atlas.apache.org Received: (qmail 72876 invoked by uid 500); 23 Oct 2015 14:52:30 -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 72864 invoked by uid 99); 23 Oct 2015 14:52:30 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Oct 2015 14:52:30 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id F01A9C082C for ; Fri, 23 Oct 2015 14:52:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.97 X-Spam-Level: X-Spam-Status: No, score=0.97 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id p-blT7RZb4be for ; Fri, 23 Oct 2015 14:52:29 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with SMTP id 0820D439C2 for ; Fri, 23 Oct 2015 14:52:28 +0000 (UTC) Received: (qmail 71908 invoked by uid 99); 23 Oct 2015 14:52:28 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Oct 2015 14:52:28 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B1F1B2C1F5E for ; Fri, 23 Oct 2015 14:52:27 +0000 (UTC) Date: Fri, 23 Oct 2015 14:52:27 +0000 (UTC) From: "Herman Yu (JIRA)" To: dev@atlas.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ATLAS-251) input/output of lineage graph are confusing MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Herman Yu created ATLAS-251: ------------------------------- Summary: input/output of lineage graph are confusing Key: ATLAS-251 URL: https://issues.apache.org/jira/browse/ATLAS-251 Project: Atlas Issue Type: Improvement Affects Versions: 0.5-incubating Reporter: Herman Yu we found the input/output tabs of the lineage graph are confusing. for a hive table, should the input tab have a graph with the hive table as the end? this leads to the question of the definition of the inputs/outputs attributes of the Process classType, does Inputs mean "inputing" or "inputed by"? Does outputs mean "Outputing" or "outputted by"? Let's get to a clear definition here first and then see if there are bugs with the "input'/"output" tab and graphs... -- This message was sent by Atlassian JIRA (v6.3.4#6332)