# Error: entity content is too long \[105072697\] for the configured buffer limit \[104857600\]

**URL:** <https://discuss.elastic.co/t/error-entity-content-is-too-long-105072697-for-the-configured-buffer-limit-104857600/385636>\
**Category:** Elasticsearch\
**Created:** [March 26, 2026, 10:10am UTC](https://discuss.elastic.co/t/error-entity-content-is-too-long-105072697-for-the-configured-buffer-limit-104857600/385636 "2026-03-26T10:10:46Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Chen\_Wen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chen_wen/32/147223_2.png) [@Chen\_Wen](https://discuss.elastic.co/u/Chen_Wen)\
**Post date:** [March 27, 2026, 1:35am UTC](https://discuss.elastic.co/t/error-entity-content-is-too-long-105072697-for-the-configured-buffer-limit-104857600/385636/5 "2026-03-27T01:35:06Z")

</div>

That’s correct, I used trino sql engine to connect ES and use its raw query to request log in one request. A part query as below. For a big time range query which would reponse a little more bigger than 100mb content in the response body and got error as above.

```auto
SELECT result
      FROM TABLE(elastic_mozart.system.raw_query(schema => 'default', index => 'ailogs-oneapi', query => '{
  "size": 10000000,
  "query": {
   "bool": {
   "filter": [
    {.....

```

I know that I could use scroll streaming api with curl, but my case is using trino elasetic plugin which I couldn’t attach the raw\_query function. Also for sure I can use dummy SQL query instead the raw\_query but which is really slow performance. And for most of my case 100mb is fine, only a little bit case to query full data which hit the limitation.

I read relative talk in below session, but have no idea how could work around to enlarge a little bit more than 100mb is OK to me.

> [@Elasticsearch-rest-client-5.6.1.jar org.apache.http.ContentTooLongException: entity content is too long \[217056451\] for the configured buffer limit \[104857600\]](https://discuss.elastic.co/t/elasticsearch-rest-client-5-6-1-jar-org-apache-http-contenttoolongexception-entity-content-is-too-long-217056451-for-the-configured-buffer-limit-104857600/101387/6):
>
> I'd not do that. But if you really want to overload your data nodes and your client, up to you. Did you read the workaround that Tanguy mentioned in the issue I linked to? Specifically that class:

---

_[View the full topic](https://discuss.elastic.co/t/error-entity-content-is-too-long-105072697-for-the-configured-buffer-limit-104857600/385636)._