write/flush asynchronous
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 398
- Forks
- 181
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 36
Description
More question first: is flushing to gcs asynchronous ? i.e. I like this not to be a blocking operation so that the buffer (and new one ?) gets filled in while the previous block is being written to backend.
If it is a blocking op, request is to not make it ;-) or provide an option to enable/disable.
Our use case is a high-volume high-speed module in flask (switching to aiohttp server) where we continuously stream to GCS during a time window.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by locating the GCS write and flush path, then determine whether flushing blocks while data is sent to the backend. Done means the asynchronous behavior is specified and implemented, with any enable/disable option covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100