<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Data Lineage Graph with hive views in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Data-Lineage-Graph-with-hive-views/m-p/127713#M47489</link>
    <description>&lt;P&gt;The
data lineage graph generated by Apache Atlas when Hive view are implicated
presents some dilemma. In fact,  the hive
process that contribute to creation of hive view doesn’t bind only with the
views declared in the query but to the views that contribute to creation of
those views and recursively until reach 
table that contributes to creation of views.&lt;/P&gt;&lt;P&gt;I want to know if this lineage is a part of  the
philosophy of apache atlas in presenting data lineage graph containing hive
views or  it could be a non-tested case and then should be adjusted. &lt;/P&gt;</description>
    <pubDate>Tue, 29 Nov 2016 22:34:46 GMT</pubDate>
    <dc:creator>radhwene_elhadj</dc:creator>
    <dc:date>2016-11-29T22:34:46Z</dc:date>
    <item>
      <title>Data Lineage Graph with hive views</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Data-Lineage-Graph-with-hive-views/m-p/127713#M47489</link>
      <description>&lt;P&gt;The
data lineage graph generated by Apache Atlas when Hive view are implicated
presents some dilemma. In fact,  the hive
process that contribute to creation of hive view doesn’t bind only with the
views declared in the query but to the views that contribute to creation of
those views and recursively until reach 
table that contributes to creation of views.&lt;/P&gt;&lt;P&gt;I want to know if this lineage is a part of  the
philosophy of apache atlas in presenting data lineage graph containing hive
views or  it could be a non-tested case and then should be adjusted. &lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2016 22:34:46 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Data-Lineage-Graph-with-hive-views/m-p/127713#M47489</guid>
      <dc:creator>radhwene_elhadj</dc:creator>
      <dc:date>2016-11-29T22:34:46Z</dc:date>
    </item>
    <item>
      <title>Re: Data Lineage Graph with hive views</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Data-Lineage-Graph-with-hive-views/m-p/127714#M47490</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/13380/radhweneelhadjelarbi.html" nodeid="13380"&gt;@Radhouene EL HADJ EL ARBI&lt;/A&gt; &lt;/P&gt;&lt;P&gt;This is by design.  Atlas, and most governance tools in general, will trace lineage as far back as possible.  With Atlas, not only will it go back to the root table(s), it can even go as far back as the Storm or Sqoop job that ingested the data to the original tables.&lt;/P&gt;&lt;P&gt;The purpose of having lineage this far back is for a user to be able to effectively trace back the origins of data, whether to validate data quality, for compliance, or even just to understand how the data has mutated/evolved to it's current state.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Dec 2016 15:14:41 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Data-Lineage-Graph-with-hive-views/m-p/127714#M47490</guid>
      <dc:creator>egarelnabi</dc:creator>
      <dc:date>2016-12-16T15:14:41Z</dc:date>
    </item>
  </channel>
</rss>

