chore: allow external Buffer flushability checking
#101
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.
Added a
Buffer::check_can_flushmethod for checking if aBuffercan be flushed withSender::flush.Usecase
In our application we're operating in an
asyncsetting with a customasyncHTTP library & writer. At the moment we need to isolate the QuestDB sending logic into its own set of threads because it doesn't expose enough information to be able to flush theBufferourselves. However, by including thischeck_can_flushcall we can now recreate the entirety ofSender::flush_implusing our custom library and async system.