influxdata / influxdata/influxdb-client-ruby
Use gzip compression
- Dominant language
- Ruby
- Stars
- 50
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
__Proposal:__
As suggest into the [best practices session](https://docs.influxdata.com/influxdb/v2/write-data/best-practices/optimize-writes/?t=Client+libraries#use-gzip-compression), I propose to add the gzip compression on the HTTP client
__Current behavior:__
Now the HTTP request are not using the "Content-Encoding: gzip" and the deflated body in the request
__Desired behavior:__
Add an optional "compression" params and implement the compressed body (I guess only for the POST request)
__Alternatives considered:__
...
__Use case:__
See the best practice [here](https://docs.influxdata.com/influxdb/v2/write-data/best-practices/optimize-writes/?t=Client+libraries#use-gzip-compression)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the Ruby HTTP client entry point and trace the POST request path used for writes. Confirm how an optional compression parameter should control the request body and Content-Encoding header; done means gzip compression is applied when requested and ordinary requests remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100