# Kibana discover shows disabled fields in "available fields" list

**URL:** <https://discuss.elastic.co/t/kibana-discover-shows-disabled-fields-in-available-fields-list/246806>\
**Category:** Kibana\
**Created:** [August 28, 2020, 5:59pm UTC](https://discuss.elastic.co/t/kibana-discover-shows-disabled-fields-in-available-fields-list/246806 "2020-08-28T17:59:55Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Limus\_Anusauskas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/limus_anusauskas/32/74724_2.png) [@Limus\_Anusauskas](https://discuss.elastic.co/u/Limus_Anusauskas)\
**Post date:** [August 28, 2020, 5:59pm UTC](https://discuss.elastic.co/t/kibana-discover-shows-disabled-fields-in-available-fields-list/246806/1 "2020-08-28T17:59:55Z")

</div>

I specifically used index mapping to disable some high cardinality fields:

```auto
    "siteEntity": {
          "properties": {            
            "defaultPlacementsForMediaType": {
              "type": "object",
              "enabled": false
            }
         } 
    } 

```

When I look at index pattern in Kibana, the field defaultPlacementsForMediaType is not in there, as expected.  
However, Kibana discover is still trying to load every distinct value for that field and show in available fields list, which pretty much kills the page.

Is there a way to tell Kibana Discover to completely ignore that field ?

Thanks,

Limus

---

<div class="post-metadata">

**Author:** ![Limus\_Anusauskas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/limus_anusauskas/32/74724_2.png) [@Limus\_Anusauskas](https://discuss.elastic.co/u/Limus_Anusauskas)\
**Post date:** [August 28, 2020, 6:20pm UTC](https://discuss.elastic.co/t/kibana-discover-shows-disabled-fields-in-available-fields-list/246806/2 "2020-08-28T18:20:20Z")

</div>

Ok, I just found there are source filters in Kibana index pattern and that took care of my problem

---

<div class="post-metadata">

**Author:** ![matw](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/matw/32/13913_2.png) [@matw](https://discuss.elastic.co/u/matw)\
**Post date:** [September 1, 2020, 5:47am UTC](https://discuss.elastic.co/t/kibana-discover-shows-disabled-fields-in-available-fields-list/246806/3 "2020-09-01T05:47:24Z")

</div>

Great that you managed to solve it. may I ask how much field there were added to Discover? the rendering as a result took then too long, right?

Thx & Best,  
Matthias

---

<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:** [September 29, 2020, 5:47am UTC](https://discuss.elastic.co/t/kibana-discover-shows-disabled-fields-in-available-fields-list/246806/4 "2020-09-29T05:47:28Z")

</div>

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