feat: add additional stats to AirbyteStateStats #143
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AirbyteStateStatsenables sources and destination to report the number of records observed per state. This enabled validation of data consistency.This change adds an optional
AirbyteStateStats.additionalStatswhich is defined as an object of keys tonumber.The intent is to allow a looser contract to enable connectors to report additional stats related to the data being moved. For example, we introduced
AirbyteRecordMessageMetaChangewhich describes modifications connectors may need to perform on the data. The goal of this change would be to enable the connectors to report statistics related to those changes to enable better observability without having to scan the destination to extract this information.