Skip to content
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.

Sign up for GitHub

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

Jump to bottom

is there an async sender.flush()? #64

Open
sevenjay opened this issue Mar 12, 2024 · 1 comment · May be fixed by #66
Open

is there an async sender.flush()? #64

sevenjay opened this issue Mar 12, 2024 · 1 comment · May be fixed by #66

Comments

@sevenjay
Copy link

When calling sender.flush(), is it possible to use an asynchronous approach?
@amunra amunra linked a pull request Mar 20, 2024 that will close this issue
Draft
5 tasks
@amunra
Copy link
Collaborator

amunra commented Mar 20, 2024

I've drafted a PR for a SenderPool. I'm still deciding if this is a good way to go, since it would introduce a second alternative API for more advanced use cases.

I'd be happy to take some feedback.

See: #66

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: HTTP SenderPool with asyncio support questdb/py-questdb-client
2 participants
@sevenjay @amunra