.jpg%3Falt%3Dmedia%26token%3D220d4374-df04-4938-b958-660d1b7aabef){kind=logo}
.jpg%3Falt%3Dmedia%26token%3D220d4374-df04-4938-b958-660d1b7aabef){kind=logo}
Terminology
Glossary of terms for PipeRider
A YAML file is located at
.piperider/config.yml and used for storing project configuration such as available data sources and dbt integration settings. Generated by piperider init.Also known as data source connector.
Enables PipeRider to connect to a variety of data sources, such as SQLite, PostgreSQL, Snowflake, etc.
Types of connector and data source integrations:
A YAML file located at
.piperider/credentials.yml that is used for storing credentials used by connectors to connect to data sources.Capability to compare the output of runs in a static HTML page.
It is a perception or an assessment of data's fitness to serve its purpose in a given context.
Provides a standard API for accessing and interacting with data from a wide variety of source systems, such as SQLite, PostgreSQL, Snowflake, etc.
In dbt, you can define metrics, which are an aggregation over a table and can be used to display the most important metrics (e.g. weekly active users, total revenue).
The act of generating metrics and recommended assertions from a data source. The execution of a run over a time period is to generate profiling results for each run at
.piperider/outputs/.A static HTML report that is generated based on the results of a profiling run and is stored in
.piperider/outputs/.Last modified 6mo ago