# Using Kibana and Elasticsearch for non-log large datasets

**URL:** <https://discuss.elastic.co/t/using-kibana-and-elasticsearch-for-non-log-large-datasets/29599>\
**Category:** Kibana\
**Created:** [September 18, 2015, 9:20pm UTC](https://discuss.elastic.co/t/using-kibana-and-elasticsearch-for-non-log-large-datasets/29599 "2015-09-18T21:20:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![huksley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/huksley/32/4852_2.png) [@huksley](https://discuss.elastic.co/u/huksley)\
**Post date:** [September 18, 2015, 9:20pm UTC](https://discuss.elastic.co/t/using-kibana-and-elasticsearch-for-non-log-large-datasets/29599/1 "2015-09-18T21:20:23Z")

</div>

Hello!

I am trying to use Kibana 4.1 (with Elasticsearch 1.7.2) for initial 100k+ dataset of LARGE objects (900+ fields)  
for visualization and analysis of data.

Here is my experiences so far

- [Discover] step in kibana right after click is horrendous slow as it tries to show 900+ fields of "first"? objects.  
Is there any way to disable such search right after click to [Discover]?

- In [Discover] and [Visualiize] steps left side bar is too narrow. Can it be made resizeable and remember that setting?

- We have a complex/nested JSON structure and looking through all fields in [Discover] is very inconvenient. Any form of field search, etc. would be usable.

- Is there any way for all visualization on dashboard to export resulting (new) datasets, i.e. aggregate data into another elasticsearch indice? Perhaps in real time?

- On data load Elasticsearch locks field type to first found. For example room number - if first incoming value is 1 it will become number. Afterwards all future non-numeric values are invalid for example - 1a (perfectly valid for room number)  
Is there any way to override this? This question is more specific to Elasticsearch I suppose.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 19, 2015, 1:23am UTC](https://discuss.elastic.co/t/using-kibana-and-elasticsearch-for-non-log-large-datasets/29599/2 "2015-09-19T01:23:51Z")

</div>

> [@huksley](#):
>
> On data load Elasticsearch locks field type to first found. For example room number - if first incoming value is 1 it will become number. Afterwards all future non-numeric values are invalid for example - 1a (perfectly valid for room number) Is there any way to override this? This question is more specific to Elasticsearch I suppose.

That's an ES thing, look at creating explicit mappings for your data.

---

<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:12pm UTC](https://discuss.elastic.co/t/using-kibana-and-elasticsearch-for-non-log-large-datasets/29599/3 "2017-07-06T14:12:55Z")

</div>