jprdonnelly/airbyte
1
0
Fork 0
mirror of synced 2025-12-19 18:14:56 -05:00
Code Issues Packages Projects Releases Wiki Activity

Docs fix: ConfiguredAirbyteCatalog refs (#33483)

Browse Source
This commit is contained in:
Aaron ("AJ") Steers
2023-12-14 08:39:29 -08:00
committed by GitHub
parent 479502caa3
commit d083d15665
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -171,7 +171,7 @@ For the sake of brevity, we will not re-describe `spec` and `check`. They are ex
#### Input:
1. `config` - A configuration JSON object that has been validated using the `ConnectorSpecification`.
2. `catalog` - An `AirbyteCatalog`. This `catalog` should be a subset of the `catalog` returned by the `discover` command. Any `AirbyteRecordMessages`s that the destination receives that do _not_ match the structure described in the `catalog` will fail.
2. `catalog` - A [`ConfiguredAirbyteCatalog`](https://docs.airbyte.com/understanding-airbyte/beginners-guide-to-catalog#configuredairbytecatalog). This is a modified version of the `catalog` returned by the `discover` command. Any `AirbyteRecordMessages`s that the destination receives that do _not_ match the structure described in the `catalog` will fail.
3. `message stream` - \(this stream is consumed on stdin--it is not passed as an arg\). It will receive a stream of JSON-serialized `AirbyteMesssage`.
#### Output:

2
tools/schema_generator/README.md
View File

@@ -22,7 +22,7 @@ $ source .venv/bin/activate # enable the venv
$ pip install -r requirements.txt
```
To use a connectors `run` command we first need an AirbyteConfiguredCatalog:
To use a connector's `run` command we first need a `ConfiguredAirbyteCatalog`:
```bash
$ ../../airbyte-integrations/connectors/<your-connector> # you need to use the tool at the root folder of a connector