<?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: Is it not needed to preserve the data in its original format anymore with the usage of medallion in Get Started Discussions</title>
    <link>https://community.databricks.com/t5/get-started-discussions/is-it-not-needed-to-preserve-the-data-in-its-original-format/m-p/45470#M5881</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/9"&gt;@Retired_mod&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just a last question, what would happen if someone decided to change the name of one columns in the source system? For example, if someone renames the column "ID" for "cust_id" in the customer table? how&amp;nbsp;&lt;SPAN&gt;Delta Lake format&lt;/SPAN&gt;&amp;nbsp;now will know that the values in the "cust_id"&amp;nbsp;column are referencing the same values as in the "ID"&amp;nbsp;column considering this statement "&lt;SPAN&gt;while adding additional features such as versioning, schema enforcement, etc.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thank you once more time for your valuable insight.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;#medallionarchitecture&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 21 Sep 2023 00:21:38 GMT</pubDate>
    <dc:creator>eimis_pacheco</dc:creator>
    <dc:date>2023-09-21T00:21:38Z</dc:date>
    <item>
      <title>Is it not needed to preserve the data in its original format anymore with the usage of medallion?</title>
      <link>https://community.databricks.com/t5/get-started-discussions/is-it-not-needed-to-preserve-the-data-in-its-original-format/m-p/45385#M5879</link>
      <description>&lt;P&gt;Hi Community&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a doubt. The bronze layer always causes confusion for me. Someone mentioned, "&lt;SPAN&gt;File Format: Store data in Delta Lake format to leverage its performance, ACID transactions, and schema evolution capabilities&lt;/SPAN&gt;" for bronze layers.&lt;/P&gt;&lt;P&gt;Then, does this mean that is not needed to preserve the data in its original format? for instance, if this comes in JSON format from the source system or if we are exporting this data from the source database in CSV format compressed in zip files?&lt;/P&gt;&lt;P&gt;This part confused me, should we not store the data in its original format as per the medallion architecture? and should we only rely on the bronze layer for data history, lineage, audit, and&amp;nbsp;&lt;SPAN&gt;reprocessing&lt;/SPAN&gt;?&lt;/P&gt;&lt;P&gt;Thank you very much in advance for clarifying this for me.&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;#medallionarchitecture #&lt;/P&gt;</description>
      <pubDate>Tue, 19 Sep 2023 23:05:23 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/is-it-not-needed-to-preserve-the-data-in-its-original-format/m-p/45385#M5879</guid>
      <dc:creator>eimis_pacheco</dc:creator>
      <dc:date>2023-09-19T23:05:23Z</dc:date>
    </item>
    <item>
      <title>Re: Is it not needed to preserve the data in its original format anymore with the usage of medallion</title>
      <link>https://community.databricks.com/t5/get-started-discussions/is-it-not-needed-to-preserve-the-data-in-its-original-format/m-p/45470#M5881</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/9"&gt;@Retired_mod&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just a last question, what would happen if someone decided to change the name of one columns in the source system? For example, if someone renames the column "ID" for "cust_id" in the customer table? how&amp;nbsp;&lt;SPAN&gt;Delta Lake format&lt;/SPAN&gt;&amp;nbsp;now will know that the values in the "cust_id"&amp;nbsp;column are referencing the same values as in the "ID"&amp;nbsp;column considering this statement "&lt;SPAN&gt;while adding additional features such as versioning, schema enforcement, etc.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Thank you once more time for your valuable insight.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;#medallionarchitecture&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Sep 2023 00:21:38 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/is-it-not-needed-to-preserve-the-data-in-its-original-format/m-p/45470#M5881</guid>
      <dc:creator>eimis_pacheco</dc:creator>
      <dc:date>2023-09-21T00:21:38Z</dc:date>
    </item>
    <item>
      <title>Re: Is it not needed to preserve the data in its original format anymore with the usage of medallion</title>
      <link>https://community.databricks.com/t5/get-started-discussions/is-it-not-needed-to-preserve-the-data-in-its-original-format/m-p/45776#M5883</link>
      <description>&lt;P&gt;Thank you very much for your answers and insights &lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/9"&gt;@Retired_mod&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Regards!&lt;/P&gt;</description>
      <pubDate>Fri, 22 Sep 2023 22:17:00 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/is-it-not-needed-to-preserve-the-data-in-its-original-format/m-p/45776#M5883</guid>
      <dc:creator>eimis_pacheco</dc:creator>
      <dc:date>2023-09-22T22:17:00Z</dc:date>
    </item>
  </channel>
</rss>

