<?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 Object metadata in MVP Articles</title>
    <link>https://community.databricks.com/t5/mvp-articles/object-metadata/m-p/165582#M277</link>
    <description>&lt;P&gt;Thanks to the new column&lt;CODE class="cz qi qj qk ql b"&gt;_object_metadata&lt;/CODE&gt; we have access to storage-level information such as MIME type, ETag, and other metadata. That functionality is for external volumes, as in some use cases that data was needed for ingestion. Just remember that it is row-level data, so if you have a parquet file, it will be returned for every row.&lt;BR /&gt;&lt;BR /&gt;more news&amp;nbsp;&lt;A href="https://medium.com/databrickscommunity/databricks-news-dabs-indexes-ltap-genie-last-update-25-july-ffac8533774f" target="_blank"&gt;https://medium.com/databrickscommunity/databricks-news-dabs-indexes-ltap-genie-last-update-25-july-ffac8533774f&lt;/A&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="metadatacolumns.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/30005iAD22CC297109E0CF/image-size/large?v=v2&amp;amp;px=999" role="button" title="metadatacolumns.png" alt="metadatacolumns.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 12 Aug 2026 22:06:39 GMT</pubDate>
    <dc:creator>Hubert-Dudek</dc:creator>
    <dc:date>2026-08-12T22:06:39Z</dc:date>
    <item>
      <title>Object metadata</title>
      <link>https://community.databricks.com/t5/mvp-articles/object-metadata/m-p/165582#M277</link>
      <description>&lt;P&gt;Thanks to the new column&lt;CODE class="cz qi qj qk ql b"&gt;_object_metadata&lt;/CODE&gt; we have access to storage-level information such as MIME type, ETag, and other metadata. That functionality is for external volumes, as in some use cases that data was needed for ingestion. Just remember that it is row-level data, so if you have a parquet file, it will be returned for every row.&lt;BR /&gt;&lt;BR /&gt;more news&amp;nbsp;&lt;A href="https://medium.com/databrickscommunity/databricks-news-dabs-indexes-ltap-genie-last-update-25-july-ffac8533774f" target="_blank"&gt;https://medium.com/databrickscommunity/databricks-news-dabs-indexes-ltap-genie-last-update-25-july-ffac8533774f&lt;/A&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="metadatacolumns.png" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/30005iAD22CC297109E0CF/image-size/large?v=v2&amp;amp;px=999" role="button" title="metadatacolumns.png" alt="metadatacolumns.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Aug 2026 22:06:39 GMT</pubDate>
      <guid>https://community.databricks.com/t5/mvp-articles/object-metadata/m-p/165582#M277</guid>
      <dc:creator>Hubert-Dudek</dc:creator>
      <dc:date>2026-08-12T22:06:39Z</dc:date>
    </item>
  </channel>
</rss>

