<?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: Databricks SQL Error outputting sesntive data to logs in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/databricks-sql-error-outputting-sesntive-data-to-logs/m-p/117368#M45486</link>
    <description>&lt;P&gt;You could use&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;CODE&gt;mode&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(default&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;PERMISSIVE&lt;/CODE&gt; allows a mode for dealing with corrupt records during parsing.
&lt;UL&gt;
&lt;LI&gt;&lt;CODE&gt;PERMISSIVE&lt;/CODE&gt;: when it meets a corrupted record, puts the malformed string into a field configured by&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;columnNameOfCorruptRecord&lt;/CODE&gt;, and sets malformed fields to null. To keep corrupt records, you can set a string type field named&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;columnNameOfCorruptRecord&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;in an user-defined schema. If a schema does not have the field, it drops corrupt records during parsing. When inferring a schema, it implicitly adds a&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;columnNameOfCorruptRecord&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;field in an output schema.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;CODE&gt;columnNameOfCorruptRecord&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(default is the value specified in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;spark.sql.columnNameOfCorruptRecord&lt;/CODE&gt; allows renaming the new field having malformed string created by&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;PERMISSIVE&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;mode. This overrides&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;spark.sql.columnNameOfCorruptRecord&lt;/CODE&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Doc -&amp;nbsp;&lt;A href="https://docs.databricks.com/aws/en/sql/language-manual/functions/from_json" target="_blank"&gt;https://docs.databricks.com/aws/en/sql/language-manual/functions/from_json&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 01 May 2025 12:12:21 GMT</pubDate>
    <dc:creator>NandiniN</dc:creator>
    <dc:date>2025-05-01T12:12:21Z</dc:date>
    <item>
      <title>Databricks SQL Error outputting sesntive data to logs</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-sql-error-outputting-sesntive-data-to-logs/m-p/109919#M43432</link>
      <description>&lt;P&gt;Hi - I am using `from_json` with FAILFAST to correctly format some data using databricks SQL. However, this function can return the error "&lt;SPAN&gt;[MALFORMED_RECORD_IN_PARSING.WITHOUT_SUGGESTION] Malformed records are detected in record parsing" with the rest of the line being the data that caused the error.&lt;BR /&gt;&lt;BR /&gt;Is there any way to prevent this from happening and is there anywhere else this can happen? The data I am working with is sensitive and I don't want it appearing in our logs.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Feb 2025 23:24:13 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-sql-error-outputting-sesntive-data-to-logs/m-p/109919#M43432</guid>
      <dc:creator>seanstachff</dc:creator>
      <dc:date>2025-02-11T23:24:13Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks SQL Error outputting sesntive data to logs</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-sql-error-outputting-sesntive-data-to-logs/m-p/117313#M45481</link>
      <description>&lt;P&gt;Checking.&lt;/P&gt;</description>
      <pubDate>Thu, 01 May 2025 07:00:55 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-sql-error-outputting-sesntive-data-to-logs/m-p/117313#M45481</guid>
      <dc:creator>NandiniN</dc:creator>
      <dc:date>2025-05-01T07:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks SQL Error outputting sesntive data to logs</title>
      <link>https://community.databricks.com/t5/data-engineering/databricks-sql-error-outputting-sesntive-data-to-logs/m-p/117368#M45486</link>
      <description>&lt;P&gt;You could use&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;CODE&gt;mode&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(default&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;PERMISSIVE&lt;/CODE&gt; allows a mode for dealing with corrupt records during parsing.
&lt;UL&gt;
&lt;LI&gt;&lt;CODE&gt;PERMISSIVE&lt;/CODE&gt;: when it meets a corrupted record, puts the malformed string into a field configured by&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;columnNameOfCorruptRecord&lt;/CODE&gt;, and sets malformed fields to null. To keep corrupt records, you can set a string type field named&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;columnNameOfCorruptRecord&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;in an user-defined schema. If a schema does not have the field, it drops corrupt records during parsing. When inferring a schema, it implicitly adds a&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;columnNameOfCorruptRecord&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;field in an output schema.&lt;/LI&gt;
&lt;/UL&gt;
&lt;/LI&gt;
&lt;LI&gt;&lt;CODE&gt;columnNameOfCorruptRecord&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;(default is the value specified in&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;spark.sql.columnNameOfCorruptRecord&lt;/CODE&gt; allows renaming the new field having malformed string created by&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;PERMISSIVE&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;mode. This overrides&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;spark.sql.columnNameOfCorruptRecord&lt;/CODE&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Doc -&amp;nbsp;&lt;A href="https://docs.databricks.com/aws/en/sql/language-manual/functions/from_json" target="_blank"&gt;https://docs.databricks.com/aws/en/sql/language-manual/functions/from_json&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 May 2025 12:12:21 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/databricks-sql-error-outputting-sesntive-data-to-logs/m-p/117368#M45486</guid>
      <dc:creator>NandiniN</dc:creator>
      <dc:date>2025-05-01T12:12:21Z</dc:date>
    </item>
  </channel>
</rss>

