Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update review-sync-history.md #38577

Merged
merged 1 commit into from
May 22, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/cloud/managing-airbyte-cloud/review-sync-history.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ In the event of a failure, Airbyte will make several attempts to sync your data

:::info

For Airbyte Cloud syncs which [price based on the size of records moved](https://airbyte.com/pricing), we use the information presented in the sync summary in Airbyte user interface. As every database stores and compresses data differently, the measure of data volume which is used is that observed by the Airbyte Platform. When the data is in transit, is is serialized to the [Airbyte Protocol format](/understanding-airbyte/airbyte-protocol/#airbyterecordmessage). This is likely to be a larger representation of your data than you will see if you were to query your database directly.
For Airbyte Cloud syncs which [are priced based on the size of the records moved](https://airbyte.com/pricing), we use the information presented in the sync summary in the Airbyte user interface. As every database stores and compresses data differently, the measure of data volume which is used is that which is observed by the Airbyte Platform during the sync. When the data is in transit, it is serialized to [Airbyte Protocol format](/understanding-airbyte/airbyte-protocol/#airbyterecordmessage) records. This is likely to be a larger representation of your data than you will see if you were to query your database directly.

:::

Expand Down
Loading