-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Support for compression (GZIP?) on PUT/POST #1209
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.
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
Comments
Hi @jplusje Try enabling HTTP compression in your ES settings and enabling compressed responses on the client: new ConnectionSettings(...).EnableCompressedResponses(); which will add |
We are using HTTP compression on the ES responses (server to client) exactly as you described but we would like to also use compression with requests from client to server. |
Gotcha. At the moment, the client doesn't support this, but it should be possible by adding We'll look into adding this. In the meantime, you can test this out by subclassing |
Hi @jplusje When I first implemented this feature I found some contradicting information online whether elasticsearch supported it or not and also while testing found that it didn't. Rather embarrassing I have to admit I think simply forgot to send the Http Header I just submitted a PR that will fix this in the upcoming release albeit with a new toggle Thank you for reporting and forcing us to reevaluate our current implementation 😫 🌴 |
@Mpdreamz is this support only done in the server, I'm using java rest high level client, can I just enable some setting to achieve compression? or should I implement it for myself? also the server and client I'm using is 6.8.12 |
We are indexing millions of documents per day for which we are using the bulk API.
Unfortunately the requests we are generating result in JSON data of more than 100MB per request and a total daily data transfer of multiple GB's.
Is there any way to PUT/POST compressed JSON data in order to reduce the total transferred data?
The text was updated successfully, but these errors were encountered: