docs: Add edit schema page (#44396)
This commit is contained in:
@@ -82,7 +82,13 @@ The following table summarises how this works. In this example, we're looking at
|
||||
|
||||
## Using Namespaces with Basic Normalization
|
||||
|
||||
As part of the connection settings, it is possible to configure the namespace used by: 1. destination connectors: to store the `_airbyte_raw_*` tables. 2. basic normalization: to store the final normalized tables.
|
||||
:::note
|
||||
Basic normalization has been deprecated in favor of [Typing & Deduping](/using-airbyte/core-concepts/typing-deduping).
|
||||
:::
|
||||
|
||||
As part of the connection settings, it is possible to configure the namespace used by:
|
||||
1. destination connectors: to store the `_airbyte_raw_*` tables.
|
||||
2. basic normalization: to store the final normalized tables.
|
||||
|
||||
When basic normalization is enabled, this is the location that both your normalized and raw data will get written to. Your raw data will show up with the prefix `_airbyte_raw_` in the namespace you define. If you don't enable basic normalization, you will only receive the raw tables.
|
||||
|
||||
|
||||
@@ -6,19 +6,11 @@ products: all
|
||||
|
||||
For each connection, you can select between three options that allow a sync to run. The three options for `Schedule Type` are:
|
||||
|
||||
- Scheduled (e.g. every 24 hours, every 2 hours)
|
||||
- Cron
|
||||
- Manual
|
||||
|
||||
## Sync Considerations
|
||||
|
||||
- Only one sync per connection can run at a time.
|
||||
- If a sync is scheduled to run before the previous sync finishes, the scheduled sync will start after the completion of the previous sync.
|
||||
- Syncs can run at most every 60 minutes in Airbyte Cloud. Reach out to [Sales](https://airbyte.com/company/talk-to-sales) if you require replication more frequently than once per hour.
|
||||
|
||||
:::note
|
||||
For Scheduled or cron scheduled syncs, Airbyte guarantees syncs will initiate with a schedule accuracy of +/- 30 minutes.
|
||||
:::
|
||||
| Schedule Setting | Definition |
|
||||
|--|--|
|
||||
| Scheduled | Runs the syncs at the specified time interval (e.g. every 24 hours, every 2 hours) |
|
||||
| Cron | Runs the syncs based on the user-defined cron expression |
|
||||
| Manual | You are required to run the syncs manually |
|
||||
|
||||
## Scheduled syncs
|
||||
|
||||
@@ -62,3 +54,14 @@ When setting up the cron expression, you will also be asked to choose a time zon
|
||||
When the connection is set to replicate with `Manual` frequency, the sync will not automatically run.
|
||||
|
||||
It can be triggered by clicking the "Sync Now" button at any time through the UI or be triggered through the API.
|
||||
|
||||
|
||||
## Sync Considerations
|
||||
|
||||
- Only one sync per connection can run at a time.
|
||||
- If a sync is scheduled to run before the previous sync finishes, the scheduled sync will start after the completion of the previous sync.
|
||||
- Syncs can run at most every 60 minutes in Airbyte Cloud. Reach out to [Sales](https://airbyte.com/company/talk-to-sales) if you require replication more frequently than once per hour.
|
||||
|
||||
:::note
|
||||
For Scheduled or cron scheduled syncs, Airbyte guarantees syncs will initiate with a schedule accuracy of +/- 30 minutes.
|
||||
:::
|
||||
Reference in New Issue
Block a user