mirror of
https://github.com/open-metadata/OpenMetadata.git
synced 2025-12-28 07:58:31 +00:00
GitBook: [#103] emoji tweaks
This commit is contained in:
Shannon Bradshaw
Sriharsha Chintalapani
parent
6aaca2bc37
commit
2e6f9c7301
@ -2,4 +2,4 @@
|
||||
|
||||
OpenMetadata has support for Google SSO and Okta SSO as identity providers. Please see the next sections about how to configure them.
|
||||
|
||||
Enabling Security is only required for your production installation. If you are testing OpenMetadata it will be easier and faster to set up without security. To get up and running quickly with OpenMetadata (without security), please follow the [Run OpenMetadata](../../../docs/try-openmetadata/run-openmetadata/) guide.
|
||||
Enabling Security is only required for your production installation. If you are testing OpenMetadata it will be easier and faster to set up without security. To get up and running quickly with OpenMetadata (without security), please follow the [Run OpenMetadata](../../../docs/overview/try-openmetadata/run-openmetadata/) guide.
|
||||
|
||||
@ -2,4 +2,4 @@
|
||||
|
||||
OpenMetadata has support for Google SSO and Okta SSO as identity providers. Please see the next sections about how to configure them.
|
||||
|
||||
Enabling Security is only required for your production installation. If you are testing OpenMetadata it will be easier and faster to set up without security. To get up and running quickly with OpenMetadata (without security), please follow the [Run OpenMetadata](../../../docs/try-openmetadata/run-openmetadata/) guide.
|
||||
Enabling Security is only required for your production installation. If you are testing OpenMetadata it will be easier and faster to set up without security. To get up and running quickly with OpenMetadata (without security), please follow the [Run OpenMetadata](../../../docs/overview/try-openmetadata/run-openmetadata/) guide.
|
||||
|
||||
@ -34,7 +34,7 @@ OpenMetadata provides connectors that enable you to perform metadata ingestion f
|
||||
|
||||
The key components of OpenMetadata include the following:
|
||||
|
||||
* **OpenMetadata User Interface (UI)** - a central place for users to discover and collaborate on all data. See [Features](features.md) for an overview of the OpenMetadata UI.
|
||||
* **OpenMetadata User Interface (UI)** - a central place for users to discover and collaborate on all data. See [Features](overview/features.md) for an overview of the OpenMetadata UI.
|
||||
* **Ingestion framework** - a pluggable framework for integrating tools and ingesting metadata to the metadata store. The ingestion framework already supports well-known data warehouses. See the [Connectors](./#connectors) section for a complete list and documentation on supported services.
|
||||
* **Metadata APIs** - for producing and consuming metadata built on schemas for User Interfaces and for Integrating tools, systems, and services. See the API [Overview](openmetadata-apis/apis/overview.md) for details.
|
||||
* **Metadata store** - stores a metadata graph that connects data assets and user and tool generated metadata.
|
||||
|
||||
@ -1,14 +1,16 @@
|
||||
# Table of contents
|
||||
|
||||
* [🔰 Introduction](README.md)
|
||||
* [🔰 Features](features.md)
|
||||
* [🔰 Roadmap](roadmap.md)
|
||||
* [📌 Try OpenMetadata](../try-openmetadata/README.md)
|
||||
* [Try OpenMetadata in our Public Sandbox](../try-openmetadata/take-it-for-a-spin.md)
|
||||
* [Try OpenMetadata in Docker](try-openmetadata/run-openmetadata/README.md)
|
||||
* [Enable Security](try-openmetadata/run-openmetadata/enable-security.md)
|
||||
* [📌 Tutorials](tutorials/README.md)
|
||||
* [Tutorial: Data Discovery with OpenMetadata](tutorials/tutorial-data-discovery-with-openmetadata.md)
|
||||
## 📌 Overview
|
||||
|
||||
* [Introduction](README.md)
|
||||
* [Features](overview/features.md)
|
||||
* [Roadmap](overview/roadmap.md)
|
||||
* [Try OpenMetadata](overview/try-openmetadata/README.md)
|
||||
* [Try OpenMetadata in our Public Sandbox](overview/try-openmetadata/take-it-for-a-spin.md)
|
||||
* [Try OpenMetadata in Docker](overview/try-openmetadata/run-openmetadata/README.md)
|
||||
* [Enable Security](overview/try-openmetadata/run-openmetadata/enable-security.md)
|
||||
* [Tutorials](overview/tutorials/README.md)
|
||||
* [Tutorial: Data Discovery with OpenMetadata](overview/tutorials/tutorial-data-discovery-with-openmetadata.md)
|
||||
|
||||
## 📦 Integrations
|
||||
|
||||
|
||||
@ -19,7 +19,7 @@ You must have a running deployment of OpenMetadata to use this guide. OpenMetada
|
||||
* MySQL as the backing store for all metadata
|
||||
* Airflow for metadata ingestion workflows
|
||||
|
||||
If you have not already deployed OpenMetadata, please follow the instructions to [Run OpenMetadata](../../try-openmetadata/run-openmetadata/) to get up and running.
|
||||
If you have not already deployed OpenMetadata, please follow the instructions to [Run OpenMetadata](../../overview/try-openmetadata/run-openmetadata/) to get up and running.
|
||||
|
||||
### Python (version 3.8.0 or later)
|
||||
|
||||
@ -448,6 +448,6 @@ Max retries exceeded with url: /api/v1/services/databaseServices/name/local_azur
|
||||
Failed to establish a new connection: [Errno 61] Connection refused'))
|
||||
```
|
||||
|
||||
To correct this problem, please follow the steps in the [Run OpenMetadata](../../try-openmetadata/run-openmetadata/) guide to deploy OpenMetadata in Docker on your local machine.
|
||||
To correct this problem, please follow the steps in the [Run OpenMetadata](../../overview/try-openmetadata/run-openmetadata/) guide to deploy OpenMetadata in Docker on your local machine.
|
||||
|
||||
Then re-run the metadata ingestion workflow in [Step 12](azure-sql.md#run-manually).
|
||||
|
||||
@ -19,7 +19,7 @@ You must have a running deployment of OpenMetadata to use this guide. OpenMetada
|
||||
* MySQL as the backing store for all metadata
|
||||
* Airflow for metadata ingestion workflows
|
||||
|
||||
If you have not already deployed OpenMetadata, please follow the instructions to [Run OpenMetadata](../../try-openmetadata/run-openmetadata/) to get up and running.
|
||||
If you have not already deployed OpenMetadata, please follow the instructions to [Run OpenMetadata](../../overview/try-openmetadata/run-openmetadata/) to get up and running.
|
||||
|
||||
### Python (version 3.8.0 or later)
|
||||
|
||||
@ -442,6 +442,6 @@ Max retries exceeded with url: /api/v1/services/databaseServices/name/local_data
|
||||
Failed to establish a new connection: [Errno 61] Connection refused'))
|
||||
```
|
||||
|
||||
To correct this problem, please follow the steps in the [Run OpenMetadata](../../try-openmetadata/run-openmetadata/) guide to deploy OpenMetadata in Docker on your local machine.
|
||||
To correct this problem, please follow the steps in the [Run OpenMetadata](../../overview/try-openmetadata/run-openmetadata/) guide to deploy OpenMetadata in Docker on your local machine.
|
||||
|
||||
Then re-run the metadata ingestion workflow in [Step 12](databricks.md#run-manually).
|
||||
|
||||
@ -19,7 +19,7 @@ You must have a running deployment of OpenMetadata to use this guide. OpenMetada
|
||||
* MySQL as the backing store for all metadata
|
||||
* Airflow for metadata ingestion workflows
|
||||
|
||||
If you have not already deployed OpenMetadata, please follow the instructions to [Run OpenMetadata](../../try-openmetadata/run-openmetadata/) to get up and running.
|
||||
If you have not already deployed OpenMetadata, please follow the instructions to [Run OpenMetadata](../../overview/try-openmetadata/run-openmetadata/) to get up and running.
|
||||
|
||||
### Python (version 3.8.0 or later)
|
||||
|
||||
@ -418,6 +418,6 @@ Max retries exceeded with url: /api/v1/services/databaseServices/name/local_delt
|
||||
Failed to establish a new connection: [Errno 61] Connection refused'))
|
||||
```
|
||||
|
||||
To correct this problem, please follow the steps in the [Run OpenMetadata](../../try-openmetadata/run-openmetadata/) guide to deploy OpenMetadata in Docker on your local machine.
|
||||
To correct this problem, please follow the steps in the [Run OpenMetadata](../../overview/try-openmetadata/run-openmetadata/) guide to deploy OpenMetadata in Docker on your local machine.
|
||||
|
||||
Then re-run the metadata ingestion workflow in [Step 12](delta-lake.md#run-manually).
|
||||
|
||||
@ -19,7 +19,7 @@ You must have a running deployment of OpenMetadata to use this guide. OpenMetada
|
||||
* MySQL as the backing store for all metadata
|
||||
* Airflow for metadata ingestion workflows
|
||||
|
||||
If you have not already deployed OpenMetadata, please follow the instructions to [Run OpenMetadata](../../try-openmetadata/run-openmetadata/) to get up and running.
|
||||
If you have not already deployed OpenMetadata, please follow the instructions to [Run OpenMetadata](../../overview/try-openmetadata/run-openmetadata/) to get up and running.
|
||||
|
||||
### Python (version 3.8.0 or later)
|
||||
|
||||
@ -438,6 +438,6 @@ Max retries exceeded with url: /api/v1/services/databaseServices/name/local_db2
|
||||
Failed to establish a new connection: [Errno 61] Connection refused'))
|
||||
```
|
||||
|
||||
To correct this problem, please follow the steps in the [Run OpenMetadata](../../try-openmetadata/run-openmetadata/) guide to deploy OpenMetadata in Docker on your local machine.
|
||||
To correct this problem, please follow the steps in the [Run OpenMetadata](../../overview/try-openmetadata/run-openmetadata/) guide to deploy OpenMetadata in Docker on your local machine.
|
||||
|
||||
Then re-run the metadata ingestion workflow in [Step 12](ibm-db2.md#run-manually).
|
||||
|
||||
@ -19,7 +19,7 @@ You must have a running deployment of OpenMetadata to use this guide. OpenMetada
|
||||
* MySQL as the backing store for all metadata
|
||||
* Airflow for metadata ingestion workflows
|
||||
|
||||
If you have not already deployed OpenMetadata, please follow the instructions to [Run OpenMetadata](../../try-openmetadata/run-openmetadata/) to get up and running.
|
||||
If you have not already deployed OpenMetadata, please follow the instructions to [Run OpenMetadata](../../overview/try-openmetadata/run-openmetadata/) to get up and running.
|
||||
|
||||
### Python (version 3.8.0 or later)
|
||||
|
||||
@ -447,6 +447,6 @@ Max retries exceeded with url: /api/v1/services/databaseServices/name/local_sing
|
||||
Failed to establish a new connection: [Errno 61] Connection refused'))
|
||||
```
|
||||
|
||||
To correct this problem, please follow the steps in the [Run OpenMetadata](../../try-openmetadata/run-openmetadata/) guide to deploy OpenMetadata in Docker on your local machine.
|
||||
To correct this problem, please follow the steps in the [Run OpenMetadata](../../overview/try-openmetadata/run-openmetadata/) guide to deploy OpenMetadata in Docker on your local machine.
|
||||
|
||||
Then re-run the metadata ingestion workflow in [Step 12](singlestore.md#run-manually).
|
||||
|
||||
@ -36,7 +36,7 @@ description: >-
|
||||
|
||||
OpenMetadata provides all the data context you need for different use cases in a single place.
|
||||
|
||||
|
||||
|
||||
|
||||
### Data Discovery
|
||||
|
||||
@ -46,19 +46,19 @@ OpenMetadata enables you to discover your data using a variety of strategies, in
|
||||
|
||||
Find assets based on name, description, component metadata (e.g., for columns, charts), and the containing service.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Discover Data through Association
|
||||
|
||||
Discover assets through frequently joined tables and columns as measured by the data profiler. You can also discover assets through relationships based on data lineage.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Advanced Search
|
||||
|
||||
Find assets matching strict criteria on metadata properties and Boolean operators.
|
||||
|
||||
|
||||
|
||||
|
||||
### Activity Feeds
|
||||
|
||||
@ -68,31 +68,31 @@ The OpenMetadata home screen features a change activity feed that enables you vi
|
||||
* Data for which you are an owner
|
||||
* Data you are following
|
||||
|
||||
|
||||
|
||||
|
||||
### Event Notification via Webhooks and Slack Integration
|
||||
|
||||
The webhook interface allows you to build applications that receive all the data changes happening in your organization through APIs. Register URLs to receive metadata event notifications. Slack integration through incoming webhooks is one of many applications of this feature.
|
||||
|
||||
|
||||
|
||||
|
||||
### Add Descriptive Metadata
|
||||
|
||||
Add descriptions and tags to tables, columns, and other assets. OpenMetadata indexes assets based on descriptions, tags, names, and other metadata to enable keyword, advanced search, and filtering to enable you and others in your organization to discover your data.
|
||||
|
||||
|
||||
|
||||
|
||||
### Complex Data Types
|
||||
|
||||
Add descriptions and tags to nested fields in complex data types like arrays and structs. Locate these assets using keyword search or advanced search.
|
||||
|
||||
|
||||
|
||||
|
||||
### Deleted Entity Metadata
|
||||
|
||||
Entities have a lot of user-generated metadata, such as descriptions, tags, ownership, tiering. There’s also rich metadata generated by OpenMetadata through the data profiler, usage data, lineage, test results, and other graph relationships with other entities. When an entity is deleted, all of this rich information is lost, and it’s not easy to recreate it. OpenMetadata supports soft deletion in the UI and soft and permanent deletion in the API, enabling you to choose whether to maintain metadata for deleted entities.
|
||||
|
||||
|
||||
|
||||
|
||||
### Importance & Owners
|
||||
|
||||
@ -104,37 +104,37 @@ Use ownership metadata to determine the primary points of contact for any assets
|
||||
|
||||
User Tier tags and usage data to identify the relative importance of data assets.
|
||||
|
||||
.gif>)
|
||||
.gif>)
|
||||
|
||||
#### Identify Asset Owners
|
||||
|
||||
Identify owners who can help with questions about an asset.
|
||||
|
||||
|
||||
|
||||
|
||||
### Role Based Access Control
|
||||
|
||||
OpenMetadata supports Role Based Access Control (RBAC) policies for metadata operations. Each user may be assigned one or more roles. Each role has a defined policy. Policies are composed of a set of rules. Rules allow/deny access to metadata operations such as updating descriptions, tags, owners, and lineage.
|
||||
|
||||
|
||||
|
||||
|
||||
### Data Lineage
|
||||
|
||||
Trace the path of data across tables, pipelines, and dashboards.
|
||||
|
||||
|
||||
|
||||
|
||||
### Edit Data Lineage Manually
|
||||
|
||||
Edit lineage to provide a richer understanding of the provenance of data. The OpenMetadata no-code editor provides a drag and drop interface. Drop tables, pipelines, and dashboards onto the lineage graph. You may add new edges or delete existing edges to better represent data lineage. 
|
||||
|
||||
|
||||
|
||||
|
||||
### DBT Integration
|
||||
|
||||
A DBT model provides transformation logic that creates a table from raw data. While lineage tells us broadly what data a table was generated from. A DBT model provides specifics. OpenMetadata includes an integration for DBT that enables you to see what models are being used to generate tables.
|
||||
|
||||
|
||||
|
||||
|
||||
### Data Reliability
|
||||
|
||||
@ -144,15 +144,15 @@ Build trust in your data by creating tests to monitor that the data is complete,
|
||||
|
||||
Enable the data profiler to capture table usage statistics over a period of time. This happens as part of metadata ingestion. Data profiles enable you to check for null values in non-null columns, for duplicates in a unique column, etc. You can gain a better understanding of column data distributions through descriptive statistics provided.
|
||||
|
||||
|
||||
|
||||
|
||||
### Service Connectors & One-Click Ingestion Pipelines
|
||||
|
||||
Integrate your database, dashboard, messaging, and pipeline services with OpenMetadata. OpenMetadata provides a UI integration with Apache Airflow as a workflow engine to run ingestion, data profiling, data quality and other automation jobs. Admins can configure a service to run the OpenMetadata pipelines and add an ingestion schedule to automatically kick off the ingestion jobs directly from the OpenMetadata UI.
|
||||
|
||||
|
||||
|
||||
|
||||
See the [Connectors](integrations/connectors/) documentation for information on available connectors and how to integrate your services with OpenMetadata.
|
||||
See the [Connectors](../integrations/connectors/) documentation for information on available connectors and how to integrate your services with OpenMetadata.
|
||||
|
||||
### Metadata Versioning & Events API
|
||||
|
||||
@ -171,7 +171,7 @@ Metadata versioning helps **simplify debugging processes**. View the version his
|
||||
|
||||
Versioning also helps in **broader collaboration** among consumers and producers of data. Admins can provide access to more users in the organization to change certain fields. Crowdsourcing makes metadata the collective responsibility of the entire organization.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Events API
|
||||
|
||||
@ -181,4 +181,4 @@ Starting in the 0.6 release, OpenMetadata captures changes in both technical met
|
||||
|
||||
OpenMetadata supports SSL-enabled Elasticsearch (including self-signed certs). In prior versions of OpenMetadata it was necessary to run an indexing workflow following any ingestion workflow to make ingested entities available in the OpenMetadata UI. As of the 0.7 release, OpenMetadata automatically runs an indexing workflow as new entities are added or updated through ingestion workflows.
|
||||
|
||||
|
||||
|
||||
@ -4,6 +4,6 @@
|
||||
[take-it-for-a-spin.md](take-it-for-a-spin.md)
|
||||
{% endcontent-ref %}
|
||||
|
||||
{% content-ref url="../docs/try-openmetadata/run-openmetadata/" %}
|
||||
[run-openmetadata](../docs/try-openmetadata/run-openmetadata/)
|
||||
{% content-ref url="run-openmetadata/" %}
|
||||
[run-openmetadata](run-openmetadata/)
|
||||
{% endcontent-ref %}
|
||||
@ -191,7 +191,7 @@ Username: `admin`
|
||||
|
||||
Password: `admin`
|
||||
|
||||
|
||||
|
||||
|
||||
### 10. Begin using OpenMetadata
|
||||
|
||||
@ -203,13 +203,13 @@ http://localhost:8585
|
||||
|
||||
You should see a page similar to the following as the landing page for the OpenMetadata server.
|
||||
|
||||
|
||||
|
||||
|
||||
### Next Steps
|
||||
|
||||
1. Visit the [Features](../../features.md) overview page and explore the OpenMetadata UI.
|
||||
2. Visit the [Connectors](../../integrations/connectors/) documentation to see what services you can integrate with OpenMetadata.
|
||||
3. Visit the [API](../../openmetadata-apis/apis/overview.md) documentation and explore the OpenMetadata APIs.
|
||||
2. Visit the [Connectors](../../../integrations/connectors/) documentation to see what services you can integrate with OpenMetadata.
|
||||
3. Visit the [API](../../../openmetadata-apis/apis/overview.md) documentation and explore the OpenMetadata APIs.
|
||||
|
||||
### Troubleshooting
|
||||
|
||||
@ -6,7 +6,7 @@ description: This guide helps you enable security in OpenMetadata with Docker
|
||||
|
||||
By default, security is not enabled when bringing up a cluster with the `metadata docker --start` command. To enable authentication and authorization, follow the below-mentioned steps:
|
||||
|
||||
1. Create an env file like the following in your machine and update the values as required. Refer to the [Enable Security](../../../deploy/deploy-on-bare-metal/enable-security/) documentation to set up your preferred authentication provider.
|
||||
1. Create an env file like the following in your machine and update the values as required. Refer to the [Enable Security](../../../../deploy/deploy-on-bare-metal/enable-security/) documentation to set up your preferred authentication provider.
|
||||
|
||||
```
|
||||
AUTHORIZER_CLASS_NAME=org.openmetadata.catalog.security.DefaultAuthorizer
|
||||
@ -29,7 +29,7 @@ By default, security is not enabled when bringing up a cluster with the `metadat
|
||||
```
|
||||
|
||||
|
||||
3. Do not wait for the sample metadata ingestion to complete. The sample data ingestion will fail since the metadata server starts in a secure mode and will expect credentials to be present in the requests. Follow the [Configure Ingestion](../../../deploy/deploy-on-bare-metal/enable-security/okta-sso/configure-security-ingestion.md) documentation for your preferred SSO to configure ingestion with secure credentials. You can exit the command line with "Ctrl + C".
|
||||
3. Do not wait for the sample metadata ingestion to complete. The sample data ingestion will fail since the metadata server starts in a secure mode and will expect credentials to be present in the requests. Follow the [Configure Ingestion](../../../../deploy/deploy-on-bare-metal/enable-security/okta-sso/configure-security-ingestion.md) documentation for your preferred SSO to configure ingestion with secure credentials. You can exit the command line with "Ctrl + C".
|
||||
4. Visit [http://localhost:8585](http://localhost:8585) to start exploring OpenMetadata in a secure mode
|
||||
|
||||
|
||||
@ -6,14 +6,14 @@ We want our users to get the experience of OpenMetadata with the least effort
|
||||
|
||||
### 1. Login using your Google credentials
|
||||
|
||||
|
||||
|
||||
|
||||
### 2. Add yourself as a user. Pick a few teams to be part of because data is a team game.
|
||||
|
||||
|
||||
|
||||
|
||||
### 3. Try out few things
|
||||
|
||||
Don't limit yourself to just the callouts. Try other things too. We would love to get your feedback.
|
||||
|
||||
|
||||
|
||||
@ -8,23 +8,23 @@ In this tutorial, we will explore key features of the OpenMetadata standard and
|
||||
|
||||
For this tutorial, we will assume the role of data analysts who have been asked to analyze product sales by region. We will use the OpenMetadata sandbox. The sandbox is an environment in which you can explore OpenMetadata in the context of data assets and the metadata with which a community of users has annotated these resources.
|
||||
|
||||
.png>)
|
||||
.png>)
|
||||
|
||||
### **1. Log in to the OpenMetadata sandbox using a Google account**
|
||||
|
||||
Navigate to the [OpenMetadata sandbox](https://sandbox.open-metadata.org/signin) and log in using your Google account.
|
||||
|
||||
|
||||
|
||||
|
||||
### 2. Add yourself as a user and add yourself to several teams
|
||||
|
||||
This is only necessary if you have previously logged in to OpenMetadata.
|
||||
|
||||
|
||||
|
||||
|
||||
Once logged in, your view of the sandbox should look something like the figure below.
|
||||
|
||||
|
||||
|
||||
|
||||
### 3. Search for "sales"
|
||||
|
||||
@ -32,21 +32,21 @@ In the search box, enter the search term, sales. OpenMetadata will perform the s
|
||||
|
||||
Note that as we type the search term sales, OpenMetadata auto-suggests a number of matching assets categorized by type in a dropdown just below the search box. In this case, there are assets of type Table, Topic, and Dashboard displayed. See the figure below for an example. OpenMetadata search also looks for pipelines, column names, tags, and other assets matching your query. Keyword search is, therefore, a powerful tool for locating relevant assets.
|
||||
|
||||
|
||||
|
||||
|
||||
### 4. Explore the search results: Tables, Dashboards, Pipelines
|
||||
|
||||
Having issued our search for sales, we see results similar to those depicted below. This query matches 12 tables across the BigQuery and Redshift services.
|
||||
|
||||
|
||||
|
||||
|
||||
In addition, we’ve identified four dashboards...
|
||||
|
||||
|
||||
|
||||
|
||||
...and an ETL pipeline for sales data.
|
||||
|
||||
|
||||
|
||||
|
||||
### 5. Take note of descriptions and tags
|
||||
|
||||
@ -54,7 +54,7 @@ As we look through all of this, it’s important to note the descriptions for th
|
||||
|
||||
We also see tags that other users have applied to help identify data types of particular interest contained in each asset.
|
||||
|
||||
|
||||
|
||||
|
||||
Finally, we see that some of the assets are identified with a tag specifying tiers ranging from Tier1 to Tier5. Tiers are a means of identifying the relative importance of assets.
|
||||
|
||||
@ -62,37 +62,37 @@ Finally, we see that some of the assets are identified with a tag specifying tie
|
||||
|
||||
To learn more about Tiers and other tags, we can visit _Settings > Tags_.
|
||||
|
||||
|
||||
|
||||
|
||||
Clicking _Tier_ from the _Tag Categories_ provides us with a description of the Tier tag type as well as a detailed description of each tier.
|
||||
|
||||
Note also that the description for each tier includes a _Usage_ label identifying the number of assets to which that tag has been applied. This number is linked to all assets tagged accordingly. Usage data is maintained for Tier tags and all other tags as well.
|
||||
|
||||
|
||||
|
||||
|
||||
### 7. Focus on Tier1 (important) assets
|
||||
|
||||
In general, for analyses that will drive business decisions, we want to ensure that the data we are using is important and already being used to drive other decisions. As we saw in the previous step, Tier1 assets meet this criterion.
|
||||
|
||||
|
||||
|
||||
|
||||
Based on our consideration of asset descriptions, tags, and tiers, we now have a better sense for how to locate the data we need in order to perform an analysis of sales by region\*\*.\*\*
|
||||
|
||||
Let’s go back to the tables tab in our search results since that’s where we’ll find the source data we need. Looking at the options for filtering search results, we can select Tier1 to limit results to just the most important tables among the assets matching our query.
|
||||
|
||||
|
||||
|
||||
|
||||
### 8. Sort by usage frequency
|
||||
|
||||
In addition to tiers, another determiner of importance is how frequently a table is used. The OpenMetadata search UI enables us to sort results by weekly usage. Let’s go ahead and do that.
|
||||
|
||||
|
||||
|
||||
|
||||
### 9. Limit consideration to high usage, Tier1 assets
|
||||
|
||||
Having sorted the Tier1 assets, we can see that there are probably only two tables that warrant further consideration: _fact\_sale_ and _fact\_order_. Both of these tables are roughly among the top quarter of the most frequently used tables. Based on their names, either could serve our purpose so we’ll need to dig deeper.
|
||||
|
||||
.png>)
|
||||
.png>)
|
||||
|
||||
### 10. Use descriptions to distinguish between candidate assets
|
||||
|
||||
@ -100,11 +100,11 @@ At this point, we can see that we’ll need to compare _fact\_sale_ and _fact\_o
|
||||
|
||||
First from the _fact\_sale_ description we see a statement that indicates that we should use _fact\_sale_.
|
||||
|
||||
|
||||
|
||||
|
||||
Then from the _fact\_order_ description we see a statement that directs us to use the _fact\_sale_ table when computing financial metrics.
|
||||
|
||||
|
||||
|
||||
|
||||
As further evidence, if you’ll recall, the description of the _fact\_order\_and\_sales\_etl_ pipeline that we reviewed in step 5 above also calls out the use of _fact\_sale_ for critical reporting.
|
||||
|
||||
@ -18,7 +18,7 @@ OpenMetadata is built using Java, DropWizard, Jetty, and MySQL.
|
||||
|
||||
### Run OpenMetadata Server
|
||||
|
||||
Please refer to the [Run OpenMetadata ](../docs/try-openmetadata/run-openmetadata/#install-on-your-local-machine)section to run the server manually or using [Docker](../docs/try-openmetadata/run-openmetadata/#run-docker).
|
||||
Please refer to the [Run OpenMetadata ](../docs/overview/try-openmetadata/run-openmetadata/#install-on-your-local-machine)section to run the server manually or using [Docker](../docs/overview/try-openmetadata/run-openmetadata/#run-docker).
|
||||
|
||||
### Install from PyPI
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user