# 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:** 1\
**Showing post:** 3

<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"
```

---

_[View the full topic](https://discuss.elastic.co/t/numeric-fields-not-searchable-and-aggregatable/134622)._