- Notifications
You must be signed in to change notification settings - Fork 4.9k
Destinations: Refreshes: Track stream statuses in async framework #38075
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
Conversation
| The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
This stack of pull requests is managed by Graphite. Learn more about stacking. |
...n/io/airbyte/cdk/integrations/destination/buffered_stream_consumer/BufferedStreamConsumer.kt Outdated Show resolved Hide resolved
50c1e4b to e857ce6 Compare fdf57a0 to 4514243 Compare e857ce6 to 982948e Compare 7eb8203 to 2a3f5d9 Compare 982948e to 0fd05a7 Compare 2a3f5d9 to 7753251 Compare 0fd05a7 to 0d4af89 Compare 7753251 to 757297c Compare 0d4af89 to 52b9185 Compare 757297c to 21d308b Compare 52b9185 to ccf601a Compare 21d308b to 34d6f0b Compare ccf601a to 6839b3f Compare 34d6f0b to cf93b76 Compare ...src/main/kotlin/io/airbyte/cdk/integrations/destination/async/model/PartialAirbyteMessage.kt Outdated Show resolved Hide resolved
6839b3f to d361d45 Compare cf93b76 to 5878c44 Compare 5878c44 to de8e132 Compare 136594e to 3c20271 Compare There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was only needed for BufferedStreamConsumer, which should no longer be relevant to DV2 destinations...
e29c5d9 to 1f11d82 Compare 221663a to 80bab4a Compare 1f11d82 to afef1a6 Compare 80bab4a to 96c5070 Compare | package io.airbyte.cdk.integrations.destination | ||
| | ||
| import java.util.* | ||
| import io.airbyte.protocol.models.v0.AirbyteStreamStatusTraceMessage.AirbyteStreamStatus |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for later: we need to clean up this v0 protocol from dependency before we introduce protocol versioning. most places we use classes from v0 and some non-v0
| AirbyteMessage.Type.STATE -> { | ||
| stateManager.trackState(message, sizeInBytes.toLong()) | ||
| } | ||
| else -> {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👌
...ain/kotlin/io/airbyte/cdk/integrations/destination/async/deser/AirbyteMessageDeserializer.kt Outdated Show resolved Hide resolved
...src/main/kotlin/io/airbyte/cdk/integrations/destination/async/model/PartialAirbyteMessage.kt Outdated Show resolved Hide resolved
afef1a6 to 60fe677 Compare 9c697a3 to 1be53b3 Compare 60fe677 to 7910b55 Compare 7910b55 to 1638b6d Compare 1be53b3 to 600a84f Compare 1638b6d to 7910b55 Compare 7910b55 to feba86e Compare 600a84f to 30466fd Compare 30466fd to c469716 Compare | /publish-java-cdk
|

closes https://github.com/airbytehq/airbyte-internal-issues/issues/7608; closes #7621
overwriteFinalTableif the status was not COMPLETEthis PR has "safe" default behavior, i.e. if platform doesn't send a stream status message then we assume success. This is compatible with older platform versions. See #38067 for how we switch to the backwards-incompatible behavior (which is required for no data downtime).