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.

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

Support asStream to bypass decompression of gzipped responses #1597

Closed
thomasneirynck opened this issue Nov 8, 2021 · 0 comments · Fixed by elastic/elastic-transport-js#34

Comments

@thomasneirynck
Copy link

thomasneirynck commented Nov 8, 2021

🚀 Feature Proposal

The Elasticsearch vector tile search API returns tiles, a binary response format. These can be gzipped (setting Accept-encoding: gzip, to even further reduce the response size.

Ideally, the JS-client does not decompress the tile, but allows a client to just get the gzipped return.

Motivation

Most web-clients that understand the vector-tile format (e.g. mapbox-gl), can use gzipped tiles transparently. There is no need to unzip in intermediate step and increase latency.

Example

Kibana Maps requests tiles from Elasticsearch. Rather than the JS-client unzipping and Kibana returning an unzipped response, Kibana could proxy the gzipped-tiles straight to the browser.

cc @delvedor @iverase

@thomasneirynck thomasneirynck changed the title Support asStream to avoid decompression Support asStream to bypass decompression of gzipped responses Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant