# Raw field not showed in kibana for term aggregation

**URL:** <https://discuss.elastic.co/t/raw-field-not-showed-in-kibana-for-term-aggregation/40656>\
**Category:** Kibana\
**Created:** [February 1, 2016, 5:38pm UTC](https://discuss.elastic.co/t/raw-field-not-showed-in-kibana-for-term-aggregation/40656 "2016-02-01T17:38:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![michele\_crudele](https://avatars.discourse-cdn.com/v4/letter/m/91b2a8/32.png) [@michele\_crudele](https://discuss.elastic.co/u/michele_crudele)\
**Post date:** [February 1, 2016, 5:38pm UTC](https://discuss.elastic.co/t/raw-field-not-showed-in-kibana-for-term-aggregation/40656/1 "2016-02-01T17:38:26Z")

</div>

I have indexed a pathname field as follows:

```auto
        "file_name" : {
          "type": "string",
          "analyzer": "pathname_analyzer",
          "search_analyzer": "keyword",
          "fields": {
            "raw": {
              "index": "not_analyzed",
              "type": "string"
            }
          }
        }

```

While I'm able to search `file_name.raw: "exact pathname"` in Kibana discover, I cannot build a term aggregation visualization because the `field_name.raw` is not showed. Only file\_name is, and I cannot create a term aggr because the field is analyzed.  
Am I doing something wrong? Thanks in advance.

---

<div class="post-metadata">

**Author:** ![stormpython](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stormpython/32/7190_2.png) [@stormpython](https://discuss.elastic.co/u/stormpython)\
**Post date:** [February 1, 2016, 5:43pm UTC](https://discuss.elastic.co/t/raw-field-not-showed-in-kibana-for-term-aggregation/40656/2 "2016-02-01T17:43:21Z")

</div>

michele\_crudele, you need to change your mapping to that of a multi field. See [here](https://www.elastic.co/guide/en/elasticsearch/reference/0.90/mapping-multi-field-type.html) for an example.

---

<div class="post-metadata">

**Author:** ![michele\_crudele](https://avatars.discourse-cdn.com/v4/letter/m/91b2a8/32.png) [@michele\_crudele](https://discuss.elastic.co/u/michele_crudele)\
**Post date:** [February 1, 2016, 5:45pm UTC](https://discuss.elastic.co/t/raw-field-not-showed-in-kibana-for-term-aggregation/40656/3 "2016-02-01T17:45:55Z")

</div>

multi\_field is deprecated... see here [https://www.elastic.co/guide/en/elasticsearch/reference/current/\_multi\_fields.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/_multi_fields.html)

I did that before and when I retrieved the mapping I realized the system replaced multi\_field with a different definition

---

<div class="post-metadata">

**Author:** ![michele\_crudele](https://avatars.discourse-cdn.com/v4/letter/m/91b2a8/32.png) [@michele\_crudele](https://discuss.elastic.co/u/michele_crudele)\
**Post date:** [February 1, 2016, 6:01pm UTC](https://discuss.elastic.co/t/raw-field-not-showed-in-kibana-for-term-aggregation/40656/4 "2016-02-01T18:01:03Z")

</div>

My apologies. I forgot to refresh the fields list when I re-created the index with the new "fields" parameter. After that, kibana started recognizing the new file\_name.raw.

---

<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:** [July 6, 2017, 2:03pm UTC](https://discuss.elastic.co/t/raw-field-not-showed-in-kibana-for-term-aggregation/40656/5 "2017-07-06T14:03:38Z")

</div>