# Reporting - CSV Export: reached the max size and contains partial data

**URL:** https://discuss.elastic.co/t/reporting-csv-export-reached-the-max-size-and-contains-partial-data/116626
**Category:** Elasticsearch
**Created:** [January 23, 2018, 9:30am UTC](https://discuss.elastic.co/t/reporting-csv-export-reached-the-max-size-and-contains-partial-data/116626 "2018-01-23T09:30:25Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)
#### Post date: [January 31, 2018, 4:15pm UTC](https://discuss.elastic.co/t/reporting-csv-export-reached-the-max-size-and-contains-partial-data/116626/5 "2018-01-31T16:15:50Z")

</div>

@Patrick_Maroney the CSV export creates a single document that is then stored in Elasticsearch, so the maximum is dependent on what Elasticsearch itself can support. There's `http.max_content_length` setting discussed [here](https://www.elastic.co/guide/en/elasticsearch/reference/master/modules-http.html) that you'l have to keep the `xpack.reporting.csv.maxSizeByte` under or it'll error out when inserting the document into Elasticsearch.

With that being said, making this value too much larger than the default 10 mB limit is untested and unsupported, and this should be done at your own risk and it has the potential to negatively affect the performance of your Elasticsearch cluster.

---

_[View the full topic](https://discuss.elastic.co/t/reporting-csv-export-reached-the-max-size-and-contains-partial-data/116626)._