# Completion field storing norms, payloads, pos and freqs

**URL:** <https://discuss.elastic.co/t/completion-field-storing-norms-payloads-pos-and-freqs/120735>\
**Category:** Elasticsearch\
**Created:** [February 20, 2018, 10:34pm UTC](https://discuss.elastic.co/t/completion-field-storing-norms-payloads-pos-and-freqs/120735 "2018-02-20T22:34:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![adrianocrestani](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrianocrestani/32/4416_2.png) [@adrianocrestani](https://discuss.elastic.co/u/adrianocrestani)\
**Post date:** [February 20, 2018, 10:34pm UTC](https://discuss.elastic.co/t/completion-field-storing-norms-payloads-pos-and-freqs/120735/1 "2018-02-20T22:34:41Z")

</div>

I have a completion field with the mapping below. When I use Luke to inspect the index, it shows that that field is storing **P** ayloads, **N** orms, **p** ositions and **f** reqs. I wonder why it needs all that data at all and how I could disable it. I am using ES 5.4.3.

![39%20PM](https://us1.discourse-cdn.com/elastic/original/3X/2/2/2258748f3e158c051413dc341f4d87427d0da5bf.png)

```
"properties": {
  "find_nea": {
    "type": "completion",
    "analyzer": "index_analyzer",
    "preserve_position_increments": false
  }
}
```

---

<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:** [March 20, 2018, 10:34pm UTC](https://discuss.elastic.co/t/completion-field-storing-norms-payloads-pos-and-freqs/120735/2 "2018-03-20T22:34:43Z")

</div>

Closed on March 20, 2018, 10:34pm UTC

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