# Duplicated index with different settings

**URL:** <https://discuss.elastic.co/t/duplicated-index-with-different-settings/155876>\
**Category:** Kibana\
**Created:** [November 8, 2018, 11:39am UTC](https://discuss.elastic.co/t/duplicated-index-with-different-settings/155876 "2018-11-08T11:39:34Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![wheelq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wheelq/32/35893_2.png) [@wheelq](https://discuss.elastic.co/u/wheelq)\
**Post date:** [November 8, 2018, 11:39am UTC](https://discuss.elastic.co/t/duplicated-index-with-different-settings/155876/1 "2018-11-08T11:39:34Z")

</div>

I would like to have two indexes, one with timestamp field defined and one without it. Is it possible?

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [November 8, 2018, 6:29pm UTC](https://discuss.elastic.co/t/duplicated-index-with-different-settings/155876/2 "2018-11-08T18:29:59Z")

</div>

If you are using two different indices, then they can have two different mappings, that's not a problem. If you are trying to query them together though, and you are using the timestamp field, the index without that field simply won't return any hits.

---

<div class="post-metadata">

**Author:** ![wheelq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wheelq/32/35893_2.png) [@wheelq](https://discuss.elastic.co/u/wheelq)\
**Post date:** [November 10, 2018, 11:49pm UTC](https://discuss.elastic.co/t/duplicated-index-with-different-settings/155876/3 "2018-11-10T23:49:50Z")

</div>

But how do I create one under same name? Currently my 'little hack' is by creating two indexes by using different range of characters inside Kibana GUI.

Lets say ES stores data as my\_little\_db\_test. Then, in Kibana, I create index by using two wildcards:

1. my\_little\_db\_test
2. my\_little\_db\_te\*

But there must be a 'cleaner' way of doing this

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [November 13, 2018, 10:14pm UTC](https://discuss.elastic.co/t/duplicated-index-with-different-settings/155876/4 "2018-11-13T22:14:01Z")

</div>

Ah, I get what you're saying. If you're querying the same data from effectively the indices, I don't understand why you need a version of the data with and without a time field. I know there are some subtle differences in the way Kibana handles non-timeseries data, but is there something you can't do when you pick a time field on the index pattern?

---

<div class="post-metadata">

**Author:** ![wheelq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wheelq/32/35893_2.png) [@wheelq](https://discuss.elastic.co/u/wheelq)\
**Post date:** [November 16, 2018, 1:57pm UTC](https://discuss.elastic.co/t/duplicated-index-with-different-settings/155876/5 "2018-11-16T13:57:06Z")

</div>

Lets just say I have no choice 🙂

---

<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:** [December 14, 2018, 1:57pm UTC](https://discuss.elastic.co/t/duplicated-index-with-different-settings/155876/6 "2018-12-14T13:57:15Z")

</div>

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