# Filbeat decode\_csv\_fields processor silently drops fields greater than 1024 characters

**URL:** https://discuss.elastic.co/t/filbeat-decode-csv-fields-processor-silently-drops-fields-greater-than-1024-characters/294983
**Category:** Beats
**Tags:** filebeat
**Created:** [January 20, 2022, 6:48pm UTC](https://discuss.elastic.co/t/filbeat-decode-csv-fields-processor-silently-drops-fields-greater-than-1024-characters/294983 "2022-01-20T18:48:11Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![feliperuiz](https://avatars.discourse-cdn.com/v4/letter/f/5f8ce5/32.png) [@feliperuiz](https://discuss.elastic.co/u/feliperuiz)
#### Post date: [January 20, 2022, 6:48pm UTC](https://discuss.elastic.co/t/filbeat-decode-csv-fields-processor-silently-drops-fields-greater-than-1024-characters/294983/1 "2022-01-20T18:48:11Z")

</div>

Hello. I am trying to process some csv files in filebeat with the `decode_csv_fields` processor, but it seems that it is silently dropping fields that are greater than 1024 characters.  
Here is my filebeat processor configuration:

```auto
- type: filestream
  enabled: true
  paths:
    - /mnt/file.csv
  pipeline: "00-custom-pipeline"
  processors:
    - decode_csv_fields:
        fields:
          message: CSVfields
        separator: ","
        ignore_missing: false
        overwrite_keys: true
        trim_leading_space: false
        fail_on_error: true

```

For debugging purposes I also configured an `extract_array` processor and it confirmed that any field greater than 1024 does not shows up.

Is this limit configurable or a hard limitation that I can't overcome?

Thanks.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 17, 2022, 8:48pm UTC](https://discuss.elastic.co/t/filbeat-decode-csv-fields-processor-silently-drops-fields-greater-than-1024-characters/294983/2 "2022-02-17T20:48:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.