<?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: Column is accessible after dropping the same column in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/column-is-accessible-after-dropping-the-same-column/m-p/3756#M686</link>
    <description>&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jun 2023 04:18:50 GMT</pubDate>
    <dc:creator>Ajay-Pandey</dc:creator>
    <dc:date>2023-06-05T04:18:50Z</dc:date>
    <item>
      <title>Column is accessible after dropping the same column</title>
      <link>https://community.databricks.com/t5/data-engineering/column-is-accessible-after-dropping-the-same-column/m-p/3754#M684</link>
      <description>&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Today I have seen very Strang behavior of databricks.&lt;/P&gt;&lt;P&gt;I have dropped one column from a dataframe and assigned the result to a new dataframe but I am able to use the dropped column in the filter command.&lt;/P&gt;&lt;P&gt;In general scenario I should get an error but it's running fine.&lt;/P&gt;&lt;P&gt;Attaching snapshot for the same&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image.png"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/126iF63628E9EA1DFA6C/image-size/large?v=v2&amp;amp;px=999" role="button" title="image.png" alt="image.png" /&gt;&lt;/span&gt;@Ben Hayes​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;@Entong Shen​&amp;nbsp;&lt;/P&gt;&lt;P&gt;@Hubert Dudek​&amp;nbsp;&lt;/P&gt;&lt;P&gt;#DAIS2023​&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2023 13:37:30 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/column-is-accessible-after-dropping-the-same-column/m-p/3754#M684</guid>
      <dc:creator>Ajay-Pandey</dc:creator>
      <dc:date>2023-06-01T13:37:30Z</dc:date>
    </item>
    <item>
      <title>Re: Column is accessible after dropping the same column</title>
      <link>https://community.databricks.com/t5/data-engineering/column-is-accessible-after-dropping-the-same-column/m-p/3755#M685</link>
      <description>&lt;P&gt;@Ajay Pandey​&amp;nbsp;, this is a known behavior. Please refer this JIRA for details: &lt;A href="https://issues.apache.org/jira/browse/SPARK-30421" target="test_blank"&gt;https://issues.apache.org/jira/browse/SPARK-30421&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jun 2023 10:44:36 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/column-is-accessible-after-dropping-the-same-column/m-p/3755#M685</guid>
      <dc:creator>Sandeep</dc:creator>
      <dc:date>2023-06-02T10:44:36Z</dc:date>
    </item>
    <item>
      <title>Re: Column is accessible after dropping the same column</title>
      <link>https://community.databricks.com/t5/data-engineering/column-is-accessible-after-dropping-the-same-column/m-p/3756#M686</link>
      <description>&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2023 04:18:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/column-is-accessible-after-dropping-the-same-column/m-p/3756#M686</guid>
      <dc:creator>Ajay-Pandey</dc:creator>
      <dc:date>2023-06-05T04:18:50Z</dc:date>
    </item>
  </channel>
</rss>

