You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@atlas.apache.org by "Mandar Ambawane (Jira)" <ji...@apache.org> on 2020/12/10 05:18:00 UTC
[jira] [Assigned] (ATLAS-4070) hive_column_lineage .json and
impala_column_lineage .json files are missing in /admin/export zip
file
[ https://issues.apache.org/jira/browse/ATLAS-4070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mandar Ambawane reassigned ATLAS-4070:
--------------------------------------
Assignee: Mandar Ambawane
> hive_column_lineage <guid>.json and impala_column_lineage <guid>.json files are missing in /admin/export zip file
> -----------------------------------------------------------------------------------------------------------------
>
> Key: ATLAS-4070
> URL: https://issues.apache.org/jira/browse/ATLAS-4070
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Reporter: Umesh Padashetty
> Assignee: Mandar Ambawane
> Priority: Major
>
> Currently hive_column_lineage <guid>.json and impala_column_lineage <guid>.json files are missing in /admin/export zip file.
> It is to be noted that spark_column_lineage <guid>.json is getting created fine
> But the important thing to note is, even though the hive_column_lineage <guid>.json and impala_column_lineage <guid>.json files are missing in /admin/export zip file, the hive_column_lineage and impala_column_lineage is getting imported to the target cluster properly.
> In the HDP world, we used to create the file hive_column_lineage <guid>.json, but we are no more creating it. Wanted to check if this is expected behaviour.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)