# Exporting data from field with HUGE content
**URL:** https://discuss.elastic.co/t/exporting-data-from-field-with-huge-content/250760
**Category:** Elasticsearch
**Created:** [October 2, 2020, 8:14am UTC](https://discuss.elastic.co/t/exporting-data-from-field-with-huge-content/250760 "2020-10-02T08:14:40Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@prabhatdreamz](https://discuss.elastic.co/u/prabhatdreamz)
#### Post date: [October 2, 2020, 8:14am UTC](https://discuss.elastic.co/t/exporting-data-from-field-with-huge-content/250760/1 "2020-10-02T08:14:40Z")
I want to export my ES (_v6.0.0_) data to csv, for which I have the tool (_es2csv_). However, one of the fields (_message_) stores commit messages, and quite a lot of the entries are HUGE. The content can run to multiple pages. I know this should've been taken care of during indexing, but this data comes from a third party. Anyway, the problem is that while exporting the data, the tool just fails to accommodate those huge messages, and just goes haywire. It simply skips quite a lot of entries that follow the problematic entry. Furthermore, the size of the exported file can be in GBs.
So, how can I resolve or sidestep this problem? Some of the probable solutions I was thinking about are as follows:
1. A tool where I can specify character limitations on specific fields while exporting them.: _Haven't come across any, yet_
2. Reindex/Clone the current index with a specific mapping for the _message_ field, where I can place those character limitations: _Can't figure out the exact steps for this_
Any help would be appreciated.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 30, 2020, 8:14am UTC](https://discuss.elastic.co/t/exporting-data-from-field-with-huge-content/250760/2 "2020-10-30T08:14:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.