jprdonnelly/airbyte
1
0
Fork 0
mirror of synced 2025-12-25 02:09:19 -05:00
Code Issues Packages Projects Releases Wiki Activity

Docs: correct minor mistakes (#11848)

Browse Source 
* Update airbyte-specification.md

* Update upgrading-airbyte.md

* Update namespaces.md
This commit is contained in:
shyngysnurzhan
2022-04-14 03:27:59 +06:00
committed by GitHub
parent 1cf52f62ae
commit 7bb4baec25
3 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/understanding-airbyte/airbyte-specification.md
View File

@@ -26,7 +26,7 @@ This document is focused on the interfaces and primitives around connectors. You
* **Airbyte Worker** - This is a core piece of the Airbyte stack that is responsible for 1\) initializing a Source and a Destinations and 2\) passing data from Source to Destination.
* Someone implementing a connector need not ever touch this code, but in this article we mention it to contextualize how data is flowing through Airbyte.
* **Connector** - A connector is code that allows Airbyte to interact with a specific underlying data source \(e.g. Postgres\). In Airbyte, an integration is either a Source or a Destination.
* **Connector** - A connector is a code that allows Airbyte to interact with a specific underlying data source \(e.g. Postgres\). In Airbyte, an integration is either a Source or a Destination.
* **Source** - A connector that _pulls_ data from an underlying data source. \(e.g. A Postgres Source reads data from a Postgres database. A Stripe Source reads data from the Stripe API\)
* **Destination** - A connector that _pushes_ data to an underlying data source. \(e.g. A Postgres Destination writes data to a Postgres database\)
* **AirbyteSpecification** - the specification that describes how to implement connectors using a standard interface.

2
docs/understanding-airbyte/namespaces.md
View File

@@ -43,7 +43,7 @@ Available options for namespace configurations are:
### - Mirror source structure
Some sources \(such as databases based on JDBC for example\) are providing namespace informations from which a stream has been extracted from. Whenever a source is able to fill this field in the catalog.json file, the destination will try to reproduce exactly the same namespace when this configuraton is set. For sources or streams where the source namespace is not known, the behavior will fall back to the "Destination Connector settings".
Some sources \(such as databases based on JDBC for example\) are providing namespace information from which a stream has been extracted. Whenever a source is able to fill this field in the catalog.json file, the destination will try to reproduce exactly the same namespace when this configuration is set. For sources or streams where the source namespace is not known, the behavior will fall back to the "Destination Connector settings".
### - Destination connector settings