# Fields not displaying in visualize

**URL:** <https://discuss.elastic.co/t/fields-not-displaying-in-visualize/133501>\
**Category:** Kibana\
**Created:** [May 28, 2018, 9:16am UTC](https://discuss.elastic.co/t/fields-not-displaying-in-visualize/133501 "2018-05-28T09:16:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![fluidjeel](https://avatars.discourse-cdn.com/v4/letter/f/9fc29f/32.png) [@fluidjeel](https://discuss.elastic.co/u/fluidjeel)\
**Post date:** [May 28, 2018, 9:16am UTC](https://discuss.elastic.co/t/fields-not-displaying-in-visualize/133501/1 "2018-05-28T09:16:23Z")

</div>

The fields are not displaying in visualize under Terms or Significant Terms but are available in discover page. What should i change to make fields available in Visualize:

I have tried with keywords and text

**Mapping:**

```
PUT /vcmts-new
{
  "mappings": {
    "build": {
      "properties": {
        "rel_ver": {
          "type": "text"
        },
        "build_time": {
          "type": "date"
        },
        "rel_status": {
          "type": "text"
        },
        "rel_tags": {
          "type": "text"
        },
        "job_num": {
          "type": "integer"
        }
      }
    }
  }
}

```

**Document:**

```
POST /vcmts-new/build
{
  "rel_ver": "2.6.7.1-1-auto14",
  "build_time": "2018-05-21",
  "rel_status": "fail",
  "rel_tags": "PI09",
  "job_num": 22
}

```

![visualize-kibana](https://us1.discourse-cdn.com/elastic/original/3X/8/4/84acc2ea86b38bf36d8301dd7c9794ac922d2afb.PNG)

 ![discover-kibana](https://us1.discourse-cdn.com/elastic/original/3X/b/2/b222bca79657f09c60e8de49def4fd6a3acb36cb.PNG)

---

<div class="post-metadata">

**Author:** ![timroes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/timroes/32/19712_2.png) [@timroes](https://discuss.elastic.co/u/timroes)\
**Post date:** [May 28, 2018, 10:34am UTC](https://discuss.elastic.co/t/fields-not-displaying-in-visualize/133501/2 "2018-05-28T10:34:57Z")

</div>

You need to make them the type `keyword` if you want them to be visualized or (but most likely not what you want) turn on the [field data](https://www.elastic.co/guide/en/elasticsearch/reference/current/fielddata.html) for that fields.

The difference summed up:

**Type: text** is analyzed and splitted up by default, i.e. if you put in something like "Hello World" you will end up with terms for "hello" and "world". Meaning if you do a terms aggregation (and enable field data) on that you would retrieve one result "Hello" and one "World". That usually only makes sense for fields that have "plain text" like comments or tweets or some text people wrote.

**Type: keyword** mean index the string as it is. Don't split it up, create one entry per exact value that existed. Which is what you most often want for that type of keywords, like your status field or versions.  
If you switch the type in your mapping to `keyword` it will also be automatically aggregatable and thus appear in the list. I think that is the solution you actually want in your case.

I also tried to explain a bit about that indexing in [this blog post](https://www.timroes.de/2016/05/29/elasticsearch-kibana-queries-in-depth-tutorial/). That might help clarifying some of the analyzing ideas.

Cheers,  
Tim

---

<div class="post-metadata">

**Author:** ![xdholy](https://avatars.discourse-cdn.com/v4/letter/x/7cd45c/32.png) [@xdholy](https://discuss.elastic.co/u/xdholy)\
**Post date:** [May 28, 2018, 11:03am UTC](https://discuss.elastic.co/t/fields-not-displaying-in-visualize/133501/3 "2018-05-28T11:03:57Z")

</div>

Did you refresh the Index Patterns after you add or change the fields? Just to be sure.

---

<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:** [June 25, 2018, 11:03am UTC](https://discuss.elastic.co/t/fields-not-displaying-in-visualize/133501/4 "2018-06-25T11:03:57Z")

</div>

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