# Numeric fields not searchable and aggregatable

**URL:** <https://discuss.elastic.co/t/numeric-fields-not-searchable-and-aggregatable/134622>\
**Category:** Kibana\
**Created:** [June 5, 2018, 12:58pm UTC](https://discuss.elastic.co/t/numeric-fields-not-searchable-and-aggregatable/134622 "2018-06-05T12:58:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kottapar](https://avatars.discourse-cdn.com/v4/letter/k/a87d85/32.png) [@kottapar](https://discuss.elastic.co/u/kottapar)\
**Post date:** [June 5, 2018, 12:58pm UTC](https://discuss.elastic.co/t/numeric-fields-not-searchable-and-aggregatable/134622/1 "2018-06-05T12:58:27Z")

</div>

hey guys,  
Two numeric fields that were working fine till yesterday suddenly started causing issues with visualizations with "field" errors.  
I checked and found that the fields were listed as not searchable and aggregatable in the index.  
However on performing a query on the index for \_field\_caps. I got the below output where they're listed as true for searchable and aggregatable.

Any ideas what could be causing this?

```
  "VMs_per_Core":{  
     "float":{  
        "type":"float",
        "searchable":true,
        "aggregatable":true,
        "indices":[  
           "its-vmw-vhost-2018.05",
           "its-vmw-vhost-2018.06"
        ]
     },

  "vCPUs_per_Core":{  
     "float":{  
        "type":"float",
        "searchable":true,
        "aggregatable":true,
        "indices":[  
           "its-vmw-vhost-2018.05",
           "its-vmw-vhost-2018.06"
        ]
     },
```

---

<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:** [June 5, 2018, 6:32pm UTC](https://discuss.elastic.co/t/numeric-fields-not-searchable-and-aggregatable/134622/2 "2018-06-05T18:32:49Z")

</div>

Hey @kottapar, have you tried refreshing your index pattern by going to Management -\> Index Patterns, selecting the problematic index pattern and clicking the "Refresh" button highlighted below?

![14%20PM](https://us1.discourse-cdn.com/elastic/original/3X/e/e/eee4648dacd7fbef8c73230205f4ea413ac634a7.png)

---

<div class="post-metadata">

**Author:** ![kottapar](https://avatars.discourse-cdn.com/v4/letter/k/a87d85/32.png) [@kottapar](https://discuss.elastic.co/u/kottapar)\
**Post date:** [June 6, 2018, 5:40am UTC](https://discuss.elastic.co/t/numeric-fields-not-searchable-and-aggregatable/134622/3 "2018-06-06T05:40:48Z")

</div>

yep, I even deleted and recreated the index too 🙂  
I've already checked your reply in [https://discuss.elastic.co/t/kibana-shows-fields-are-not-searchable-and-aggregatable/89148/6](https://discuss.elastic.co/t/kibana-shows-fields-are-not-searchable-and-aggregatable/89148/6) and that's how I queried for the \_field\_caps.  
I'm using the csv filter in logstash and the mutate filter to convert it to float.

```
"VMs_per_core" => "float"
"vCPUs_per_core" => "float"
"Num_VCPUs" => "integer"
```

---

<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:** [June 6, 2018, 11:15am UTC](https://discuss.elastic.co/t/numeric-fields-not-searchable-and-aggregatable/134622/4 "2018-06-06T11:15:17Z")

</div>

Which version of Kibana/Elasticsearch are you using?

Also, would you mind executing a CURL request similar to the following against Elasticsearch and posting the raw response here? curl [http://localhost:9200/logstash-](http://localhost:9200/logstash-)_/\_field\_caps?fields=_ -u elastic:changeme. You'll want to replace logstash-\* with your index pattern and the elasticsearch URL and username/password will likely need to change.

---

<div class="post-metadata">

**Author:** ![kottapar](https://avatars.discourse-cdn.com/v4/letter/k/a87d85/32.png) [@kottapar](https://discuss.elastic.co/u/kottapar)\
**Post date:** [June 18, 2018, 6:28am UTC](https://discuss.elastic.co/t/numeric-fields-not-searchable-and-aggregatable/134622/6 "2018-06-18T06:28:56Z")

</div>

Here's the output. It says the values are searchable and aggregatable.

```
  "VMs_per_Core":{  
 "float":{  
    "type":"float",
    "searchable":true,
    "aggregatable":true,
    "indices":[  
       "its-vmw-vhost-2018.05",
       "its-vmw-vhost-2018.06"
    ]
 },

  "vCPUs_per_Core":{  
     "float":{  
        "type":"float",
        "searchable":true,
        "aggregatable":true,
        "indices":[  
           "its-vmw-vhost-2018.05",
           "its-vmw-vhost-2018.06"
        ]
     },
```

---

<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 16, 2018, 6:28am UTC](https://discuss.elastic.co/t/numeric-fields-not-searchable-and-aggregatable/134622/7 "2018-07-16T06:28:57Z")

</div>

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