atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Madhan Neethiraj (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-642) import-hive should create the lineage for external tables
Date Tue, 24 May 2016 12:25:12 GMT

    [ https://issues.apache.org/jira/browse/ATLAS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298088#comment-15298088
] 

Madhan Neethiraj commented on ATLAS-642:
----------------------------------------

[~suma.shivaprasad] since most details needed for lineage (HDFS paths, Hive table info) are
available from Hive metadata, I think it is valuable to get the available info into Atlas
- even if SQL query used to create the table is not available.

> import-hive should create the lineage for external tables
> ---------------------------------------------------------
>
>                 Key: ATLAS-642
>                 URL: https://issues.apache.org/jira/browse/ATLAS-642
>             Project: Atlas
>          Issue Type: Sub-task
>            Reporter: Suma Shivaprasad
>             Fix For: 0.7-incubating
>
>
> import-hive can also start showing lineage between HDFS paths and tables. 
> However the create table process should also register the exact query that was  used
to create the table. Show create table does that by reconstructing the query. Need to figure
out if we can potentially use that to create the query



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message