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

respond to post-merge code review for destination docs (#4418)

Browse Source
This commit is contained in:
Sherif A. Nada
2021-06-29 16:35:22 -05:00
committed by GitHub
parent 921263845e
commit c2b3c23a92
4 changed files with 13 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -209,7 +209,7 @@ For the sake of brevity, we will not re-describe `spec` and `check`. They are ex
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.
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:
1. none.
1. `AirbyteMessage`s of type `AirbyteStateMessage`. The destination connector should only output state messages if they were previously received as input on stdin. Outputting a state message indicates that all records which came before it have been successfully written to the destination.
* The destination should read in the `AirbyteMessages` and write any that are of type `AirbyteRecordMessage` to the underlying data store.
* The destination should fail if any of the messages it receives do not match the structure described in the `catalog`.