<?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>topic Re: Model Lineage to Downstream Element in Data Governance</title>
    <link>https://community.databricks.com/t5/data-governance/model-lineage-to-downstream-element/m-p/122769#M2513</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/170768"&gt;@FedeRaimondi&lt;/a&gt;,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Downstream lineage:&lt;/STRONG&gt; clear visibility from the model to the inference tables created by jobs or workflows consuming the model—is not supported currently in the same way as upstream lineage. I checked regarding this internally and found there is expressed future goal to also make downstream (e.g., batch inference jobs, serving endpoints, and their outputs) visible as part of model lineage.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;As of now, downstream lineage—making inference tables directly visible as downstream assets from the model object is not supported.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;This is a known limitation, and improving downstream lineage (showing inference tables/output directly in the model’s lineage) is on the product’s long-term roadmap/future considerations, but currently it is not available.&lt;/P&gt;
&lt;P&gt;Concluding your suggestion for end-to-end lineage is recognized as valuable and is already being discussed internally.&lt;/P&gt;</description>
    <pubDate>Wed, 25 Jun 2025 07:05:26 GMT</pubDate>
    <dc:creator>Vinay_M_R</dc:creator>
    <dc:date>2025-06-25T07:05:26Z</dc:date>
    <item>
      <title>Model Lineage to Downstream Element</title>
      <link>https://community.databricks.com/t5/data-governance/model-lineage-to-downstream-element/m-p/122250#M2506</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I tried to search for the topic in the community but couldn't find much around downstream lineage element that can be connected to a Unity Model.&lt;/P&gt;&lt;P&gt;As far as I understood, if I have an inference workflow that loads a model from unity catalog and then writes the inference on a unity catalog table that won't be visible in the model downstream lineage assets.&lt;/P&gt;&lt;P&gt;The workflow in my case is correctly visible and inside the workflow I see the downstream inference table. If this is not doable today, it would be a great addition to the platform to have a complete lineage (and lineage charts).&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jun 2025 13:49:14 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/model-lineage-to-downstream-element/m-p/122250#M2506</guid>
      <dc:creator>FedeRaimondi</dc:creator>
      <dc:date>2025-06-19T13:49:14Z</dc:date>
    </item>
    <item>
      <title>Re: Model Lineage to Downstream Element</title>
      <link>https://community.databricks.com/t5/data-governance/model-lineage-to-downstream-element/m-p/122769#M2513</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/170768"&gt;@FedeRaimondi&lt;/a&gt;,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Downstream lineage:&lt;/STRONG&gt; clear visibility from the model to the inference tables created by jobs or workflows consuming the model—is not supported currently in the same way as upstream lineage. I checked regarding this internally and found there is expressed future goal to also make downstream (e.g., batch inference jobs, serving endpoints, and their outputs) visible as part of model lineage.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;As of now, downstream lineage—making inference tables directly visible as downstream assets from the model object is not supported.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;This is a known limitation, and improving downstream lineage (showing inference tables/output directly in the model’s lineage) is on the product’s long-term roadmap/future considerations, but currently it is not available.&lt;/P&gt;
&lt;P&gt;Concluding your suggestion for end-to-end lineage is recognized as valuable and is already being discussed internally.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jun 2025 07:05:26 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/model-lineage-to-downstream-element/m-p/122769#M2513</guid>
      <dc:creator>Vinay_M_R</dc:creator>
      <dc:date>2025-06-25T07:05:26Z</dc:date>
    </item>
  </channel>
</rss>

