# Searchable, aggregatable

**URL:** <https://discuss.elastic.co/t/searchable-aggregatable/83204>\
**Category:** Kibana\
**Created:** [April 21, 2017, 12:23pm UTC](https://discuss.elastic.co/t/searchable-aggregatable/83204 "2017-04-21T12:23:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Akaren](https://avatars.discourse-cdn.com/v4/letter/a/8dc957/32.png) [@Akaren](https://discuss.elastic.co/u/Akaren)\
**Post date:** [April 21, 2017, 12:23pm UTC](https://discuss.elastic.co/t/searchable-aggregatable/83204/1 "2017-04-21T12:23:33Z")

</div>

Hi, I would like to make our ELK efficient. I know in which fields I will never search or aggregate but I still want to display them.  
Is there any way how to define "not searchable" (or aggregatable) field? I read that it is because of index is set to "not\_analyzed" but now index has only bool value. "False" will not display at all in Kibana.  
Maybe "include\_in\_all" field?

---

<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:** [April 21, 2017, 2:17pm UTC](https://discuss.elastic.co/t/searchable-aggregatable/83204/2 "2017-04-21T14:17:47Z")

</div>

@Akaren which version of Kibana/Elasticsearch are you using? I was able to use the following to create an index where field2 has index set to false, and I see it showing up in Kibana:

```auto
PUT test
{
    "settings" : {
        "number_of_shards" : 1
    },
    "mappings" : {
        "type1" : {
            "properties" : {
                "field1" : { "type" : "text" },
                "field2" : { "type" : "keyword", "index": false}
            }
        }
    }
}

```

Did you refresh your Kibana Index Pattern after changing the mappings in Elasticsearch to include that column? You can do so by going to Management -\> Index Patterns and clicking the Refresh button highlighted below in the red rectangle:

 ![](https://us1.discourse-cdn.com/elastic/original/3X/3/f/3fc084a3c902c8d6ea4b4734d3ca27dc6123137d.png)

---

<div class="post-metadata">

**Author:** ![Akaren](https://avatars.discourse-cdn.com/v4/letter/a/8dc957/32.png) [@Akaren](https://discuss.elastic.co/u/Akaren)\
**Post date:** [April 21, 2017, 4:42pm UTC](https://discuss.elastic.co/t/searchable-aggregatable/83204/3 "2017-04-21T16:42:14Z")

</div>

So when you set:  
"index: false" - it won't be searchable  
"type: keyword" - will be aggregetable

what about analyzed? Can it be all - aggregatable, analyzed and searchable?

Kibana 5.3

---

<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:** [April 21, 2017, 5:16pm UTC](https://discuss.elastic.co/t/searchable-aggregatable/83204/4 "2017-04-21T17:16:35Z")

</div>

@Akaren I'm not following. I thought your goal was to have a field that was always just displayed as-is, but you didn't want it to be searchable or aggregatable, what's what setting `{ "type" : "keyword", "index": false}` on the field2 does.

Are you now asking for a way to have a field that is searchable and aggregatable?

---

<div class="post-metadata">

**Author:** ![Akaren](https://avatars.discourse-cdn.com/v4/letter/a/8dc957/32.png) [@Akaren](https://discuss.elastic.co/u/Akaren)\
**Post date:** [April 21, 2017, 7:02pm UTC](https://discuss.elastic.co/t/searchable-aggregatable/83204/5 "2017-04-21T19:02:11Z")

</div>

I am trying to understand how it works 🙂

---

<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:** [May 19, 2017, 7:03pm UTC](https://discuss.elastic.co/t/searchable-aggregatable/83204/6 "2017-05-19T19:03:11Z")

</div>

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