![]() Keep in mind search results are just “summaries” of what Data Catalog knows about the indexed assets and each SearchResult has a small set of fields - most notably: searchResultType, searchResultSubtype, relativeResourceName, and linkedResource. Please take a look at the below image:Ī result set is returned when someone searches the Catalog. The first contact with Data Catalog usually happens thru its search feature: powerful and simple to use. Assets’ IAM roles and ACLs are considered before providing any information for a given user or service account. Privacy and information security are first-class citizens for Data Catalog. Metadata is stored/updated when assets are indexed for the first time, changed in their source systems, or tagged using Data Catalog. It also stores metadata for assets managed by other GCP services so that users may get details about them using only Data Catalog’s UI or API. name, description, and columns definitions. To build its index, Data Catalog relies on assets’ metadata, i.e. By data assets I mean: datasets, tables, views, text/CSV files, spreadsheets, and data streams. Basic conceptsĭata Catalog is kind of a centralized service, fully managed by Google Cloud, keeping an optimized search index for data assets belonging to GCP projects. The model is not based on any official/supported reference. The model summarizes my learning path since I started using Data Catalog, and will also be a basis for the next articles I'll write to this series.ĭisclaimer: this is my personal way of thinking, as a Data Catalog early adopter - only & simply this. To provide some context about Data Catalog, and help data citizens to increase velocity when getting started with the service, let me describe my mental model around its core features.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |