1"use strict";(self.webpackChunkdataedo=self.webpackChunkdataedo||[]).push([["19678"],{27298:function(a){a.exports=JSON.parse('{"tag":{"label":"Semantic Types","permalink":"/tags/semantic-types","allTagsPath":"/tags","count":3,"items":[{"id":"data-governance/data-classification/data-classification","title":"Automated Data Classification and Semantic Types","description":"Data Classification and Semantic Types enable easy categorization of your data and help you ensure compliance with various information protection acts. If Classification is added to an object, the relevant badge is displayed on all its representations within your repository and can be seen by all users.","permalink":"/data-governance/data-classification/"},{"id":"data-catalog/documenting/metadata-sync","title":"Metadata Sync","description":"Currently, this feature is supported for Databricks (Unity Catalog), Snowflake and Azure SQL Database connections.","permalink":"/data-catalog/documenting/metadata-sync"},{"id":"data-governance/data-classification/using-data-classification","title":"Running and Viewing Data Classification","description":"Data Classification is important, raising general awareness of sensitive data within your organization. As such, it is crucial that you understand how to run the process, and read its results.","permalink":"/data-governance/data-classification/using-data-classification"}],"unlisted":false}}')}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.