OpenMetadata icon indicating copy to clipboard operation
OpenMetadata copied to clipboard

OpenMetadata is a unified metadata platform for data discovery, data observability, and data governance powered by a central metadata repository, in-depth column level lineage, and seamless team colla...

Results 891 OpenMetadata issues
Sort by recently updated
recently updated
newest added

From https://openmetadata.slack.com/archives/C02B6955S4S/p1653562294488499 1. configure test 2. run test 3. change test definition in workflow 4. run workflow 5. mismatching information on the UI ![image](https://user-images.githubusercontent.com/35870520/170488703-44da0012-cb62-41f7-99e3-072e1a5ecac8.png) Let's tackle this after the backend...

bug
Ingestion
data quality
support

so that we can group ingestion, usage, etc in a single package instead of having a ton of files around in `database`... etc

Ingestion
cleanup

**Is your feature request related to a problem? Please describe.** As a consumer of Openmetadata-ingestion package, I want to add my custom connectors within the same namespace but in a...

documentation
Ingestion

we have the parameter but we are not using it for redshift or bigquery. REview all queries and validate we are passing this properly

Ingestion

**Feature** Add feature issue reference **Describe the task** A clear and concise description of what the bug is.

UI

## Context #5973 gives the ability to user to run custom SQL as a data quality test. Though, currently the SQL input is passed to a label field. ![](https://user-images.githubusercontent.com/13626425/178032382-dd06e360-a5aa-489e-811e-1e4b7d48817b.png) ##...

UI

**Is your feature request related to a problem? Please describe.** I can tag columns (assets) with a glossary, but if I want to find out more about the it, there...

DBT allows to add much more metadata to its assets than only column names and descriptions and lineage. In particular it allows to specify data owners, additional key-value metadata pairs...

Ingestion

Once we get the lineage workflow, evaluate if we can use directly any database queries that would give the source -> target relationship instead of relying always on query parsing

Ingestion