Re-order documentation on GCS and add detail blocks to overlooked destinations (#40655)
This commit is contained in:
@@ -67,6 +67,9 @@ And the [Databend Cloud](https://app.databend.com/) will only support databend v
|
||||
|
||||
## Changelog
|
||||
|
||||
<details>
|
||||
<summary>Expand to review</summary>
|
||||
|
||||
| Version | Date | Pull Request | Subject |
|
||||
| :------------------------------------------------------- | :--------------------------------------- | :-------------------------------------------------------- | :------------------------------------------------------- | ----------- |
|
||||
| 0.1.8 | 2024-06-27 | [40215](https://github.com/airbytehq/airbyte/pull/40215) | Replaced deprecated AirbyteLogger with logging.Logger |
|
||||
@@ -80,3 +83,5 @@ And the [Databend Cloud](https://app.databend.com/) will only support databend v
|
||||
| [21182](https://github.com/airbytehq/airbyte/pull/21182) | Remove protocol option and enforce HTTPS |
|
||||
| | 0.1.0 | 2022-01-09 | [20909](https://github.com/airbytehq/airbyte/pull/20909) | Destination |
|
||||
| Databend |
|
||||
|
||||
</details>
|
||||
@@ -6,17 +6,6 @@ This destination writes data to GCS bucket.
|
||||
|
||||
The Airbyte GCS destination allows you to sync data to cloud storage buckets. Each stream is written to its own directory under the bucket.
|
||||
|
||||
### Sync overview
|
||||
|
||||
#### Features
|
||||
|
||||
| Feature | Support | Notes |
|
||||
| :----------------------------- | :-----: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Full Refresh Sync | ✅ | Warning: this mode deletes all previously synced data in the configured bucket path. |
|
||||
| Incremental - Append Sync | ✅ | Warning: Airbyte provides at-least-once delivery. Depending on your source, you may see duplicated data. Learn more [here](/using-airbyte/core-concepts/sync-modes/incremental-append#inclusive-cursors) |
|
||||
| Incremental - Append + Deduped | ❌ | |
|
||||
| Namespaces | ❌ | Setting a specific bucket path is equivalent to having separate namespaces. |
|
||||
|
||||
## Getting started
|
||||
|
||||
### Requirements
|
||||
@@ -46,6 +35,17 @@ The Airbyte GCS destination allows you to sync data to cloud storage buckets. Ea
|
||||
- Corresponding key to the above access ID.
|
||||
- Make sure your GCS bucket is accessible from the machine running Airbyte. This depends on your networking setup. The easiest way to verify if Airbyte is able to connect to your GCS bucket is via the check connection tool in the UI.
|
||||
|
||||
### Sync mode support
|
||||
|
||||
#### Features
|
||||
|
||||
| Feature | Support | Notes |
|
||||
| :----------------------------- | :-----: | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Full Refresh Sync | ✅ | Warning: this mode deletes all previously synced data in the configured bucket path. |
|
||||
| Incremental - Append Sync | ✅ | Warning: Airbyte provides at-least-once delivery. Depending on your source, you may see duplicated data. Learn more [here](/using-airbyte/core-concepts/sync-modes/incremental-append#inclusive-cursors) |
|
||||
| Incremental - Append + Deduped | ❌ | |
|
||||
| Namespaces | ❌ | Setting a specific bucket path is equivalent to having separate namespaces. |
|
||||
|
||||
## Configuration
|
||||
|
||||
| Parameter | Type | Notes |
|
||||
@@ -98,6 +98,8 @@ Each stream will be outputted to its dedicated directory according to the config
|
||||
- Under Full Refresh Sync mode, old output files will be purged before new files are created.
|
||||
- Under Incremental - Append Sync mode, new output files will be added that only contain the new data.
|
||||
|
||||
|
||||
|
||||
### Avro
|
||||
|
||||
[Apache Avro](https://avro.apache.org/) serializes data in a compact binary format. Currently, the Airbyte S3 Avro connector always uses the [binary encoding](http://avro.apache.org/docs/current/spec.html#binary_encoding), and assumes that all data records follow the same schema.
|
||||
|
||||
@@ -35,6 +35,9 @@ In order to connect, you need:
|
||||
|
||||
## CHANGELOG
|
||||
|
||||
<details>
|
||||
<summary>Expand to review</summary>
|
||||
|
||||
| Version | Date | Pull Request | Subject |
|
||||
| :------ | :--------- | :-------------------------------------------------------- | :----------------------------- |
|
||||
| 0.1.6 | 2024-06-25 | [40497](https://github.com/airbytehq/airbyte/pull/40497) | Update dependencies |
|
||||
@@ -44,3 +47,5 @@ In order to connect, you need:
|
||||
| 0.1.2 | 2024-03-05 | [#35838](https://github.com/airbytehq/airbyte/pull/35838) | Un-archive connector |
|
||||
| 0.1.1 | 2023-06-21 | [#27542](https://github.com/airbytehq/airbyte/pull/27542) | Mark api_key as Airbyte Secret |
|
||||
| 0.1.0 | 2023-06-14 | [#24192](https://github.com/airbytehq/airbyte/pull/24192) | New Destination Connector Xata |
|
||||
|
||||
</details>
|
||||
Reference in New Issue
Block a user