<?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 Hostname redaction in delta table in Data Governance</title>
    <link>https://community.databricks.com/t5/data-governance/hostname-redaction-in-delta-table/m-p/69205#M1814</link>
    <description>&lt;P&gt;I am ingesting job-cluster failure notifications that we send to OpsGenie into a delta table to automate the creation and tracking of Jira tickets.&amp;nbsp; The alert notification includes the job run url, which we use to quickly respond to job failures.&amp;nbsp; However, when ingesting this data into a delta table, the hostname of the job run url is redacted.&amp;nbsp; This is not secret information to our data platform team.&amp;nbsp; How can I prevent this?&amp;nbsp; Thanks.&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 16 May 2024 22:57:23 GMT</pubDate>
    <dc:creator>marvin1</dc:creator>
    <dc:date>2024-05-16T22:57:23Z</dc:date>
    <item>
      <title>Hostname redaction in delta table</title>
      <link>https://community.databricks.com/t5/data-governance/hostname-redaction-in-delta-table/m-p/69205#M1814</link>
      <description>&lt;P&gt;I am ingesting job-cluster failure notifications that we send to OpsGenie into a delta table to automate the creation and tracking of Jira tickets.&amp;nbsp; The alert notification includes the job run url, which we use to quickly respond to job failures.&amp;nbsp; However, when ingesting this data into a delta table, the hostname of the job run url is redacted.&amp;nbsp; This is not secret information to our data platform team.&amp;nbsp; How can I prevent this?&amp;nbsp; Thanks.&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 16 May 2024 22:57:23 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/hostname-redaction-in-delta-table/m-p/69205#M1814</guid>
      <dc:creator>marvin1</dc:creator>
      <dc:date>2024-05-16T22:57:23Z</dc:date>
    </item>
    <item>
      <title>Re: Hostname redaction in delta table</title>
      <link>https://community.databricks.com/t5/data-governance/hostname-redaction-in-delta-table/m-p/69286#M1817</link>
      <description>&lt;P&gt;Thanks for your response.&amp;nbsp; I read through best practices and did not see anything specific that might apply in my case.&amp;nbsp; What I have noticed is that it is related to the secret redaction changes on runtime &amp;gt; 11.3 as I only encounter the issue when running the notebook on later runtimes.&amp;nbsp; Consequently, we are currently migrating to Unity so it is something I will have to find a workaround for, either in the standard 13.3 cluster configuration that we are running, or in my automation process (will require more code).&amp;nbsp; I am getting the sense that the latter will be the more feasible approach.&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2024 14:30:28 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/hostname-redaction-in-delta-table/m-p/69286#M1817</guid>
      <dc:creator>marvin1</dc:creator>
      <dc:date>2024-05-17T14:30:28Z</dc:date>
    </item>
    <item>
      <title>Re: Hostname redaction in delta table</title>
      <link>https://community.databricks.com/t5/data-governance/hostname-redaction-in-delta-table/m-p/69995#M1823</link>
      <description>&lt;P&gt;I tracked this issue down to running the notebook on a shared Unity-enabled cluster.&amp;nbsp; When scheduling the notebook to run on a job cluster with single user mode, this issue does not occur.&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2024 15:15:55 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/hostname-redaction-in-delta-table/m-p/69995#M1823</guid>
      <dc:creator>marvin1</dc:creator>
      <dc:date>2024-05-20T15:15:55Z</dc:date>
    </item>
  </channel>
</rss>

