-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Destinations CDK: Async framework tracks stream success #37721
Conversation
The latest updates on your projects. Learn more about Vercel for Git βοΈ 1 Ignored Deployment
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
ee5344b
to
e634730
Compare
e634730
to
e1f643f
Compare
8f95f23
to
5cdcc77
Compare
e1f643f
to
107b651
Compare
@@ -20,6 +22,7 @@ class BufferEnqueue( | |||
private val memoryManager: GlobalMemoryManager, | |||
private val buffers: ConcurrentMap<StreamDescriptor, StreamAwareQueue>, | |||
private val stateManager: GlobalAsyncStateManager, | |||
private val streamsWithSuccessStatus: ConcurrentHashSet<StreamDescriptor>, |
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 should probably be a map streamdescriptor -> status, so that we can explicitly check whether each stream succeeded or failed (and error if a stream had neither status)
5cdcc77
to
35637b5
Compare
107b651
to
f636711
Compare
a8278f6
to
98ec352
Compare
f636711
to
ec98930
Compare
What
How
Review guide
User Impact
Can this PR be safely reverted and rolled back?