We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Given that the sink is IO bound, would it make more sense to use EmitBatchAsync instead of EmitBatch?
EmitBatchAsync
EmitBatch
You seem to go to lengths to ensure everything runs synchronously using GetAwaiter().GetResult(), so I'm wondering if there was a reason for that?
GetAwaiter().GetResult()
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Given that the sink is IO bound, would it make more sense to use
EmitBatchAsync
instead ofEmitBatch
?You seem to go to lengths to ensure everything runs synchronously using
GetAwaiter().GetResult()
, so I'm wondering if there was a reason for that?The text was updated successfully, but these errors were encountered: