# Make configuration only take effect for next daily index

**URL:** <https://discuss.elastic.co/t/make-configuration-only-take-effect-for-next-daily-index/205292>\
**Category:** Logstash\
**Created:** [October 25, 2019, 3:18pm UTC](https://discuss.elastic.co/t/make-configuration-only-take-effect-for-next-daily-index/205292 "2019-10-25T15:18:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bruce289](https://avatars.discourse-cdn.com/v4/letter/b/7bcc69/32.png) [@bruce289](https://discuss.elastic.co/u/bruce289)\
**Post date:** [October 25, 2019, 3:18pm UTC](https://discuss.elastic.co/t/make-configuration-only-take-effect-for-next-daily-index/205292/1 "2019-10-25T15:18:04Z")

</div>

Hi,

We index into daily indices from logstash e.g. my\_index-%{+YYYY.MM.dd}. I would like to adjust the value of a setting on the elasticsearch output, but I only want that setting to take effect for the next day's index (not the current one). What is the best approach here?

Thanks.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [October 25, 2019, 3:48pm UTC](https://discuss.elastic.co/t/make-configuration-only-take-effect-for-next-daily-index/205292/2 "2019-10-25T15:48:13Z")

</div>

What setting are you changing?

---

<div class="post-metadata">

**Author:** ![bruce289](https://avatars.discourse-cdn.com/v4/letter/b/7bcc69/32.png) [@bruce289](https://discuss.elastic.co/u/bruce289)\
**Post date:** [October 25, 2019, 4:43pm UTC](https://discuss.elastic.co/t/make-configuration-only-take-effect-for-next-daily-index/205292/3 "2019-10-25T16:43:18Z")

</div>

Hi Christian,

I want to change `document_type`.

---

<div class="post-metadata">

**Author:** ![bruce289](https://avatars.discourse-cdn.com/v4/letter/b/7bcc69/32.png) [@bruce289](https://discuss.elastic.co/u/bruce289)\
**Post date:** [October 25, 2019, 5:04pm UTC](https://discuss.elastic.co/t/make-configuration-only-take-effect-for-next-daily-index/205292/4 "2019-10-25T17:04:54Z")

</div>

Hmm, thinking about this some more... it's possible I may not need to do this.

I'm planning to upgrade the cluster from 6.8 to 7.4 (logstash is 6.8 too and we will upgrade that afterwards). I'm concerned that once the cluster is upgraded, logstash will start sending `_doc` where it was previously sending `doc` and elasticsearch will reject the documents as multiple document types aren't allowed. However, from what I gather, `_doc` is an endpoint rather than a document type, so when logstash tries to index documents to an index with a `doc` mapping type in elasticsearch 7, I should actually be fine, right?

---

<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:** [November 22, 2019, 5:05pm UTC](https://discuss.elastic.co/t/make-configuration-only-take-effect-for-next-daily-index/205292/5 "2019-11-22T17:05:00Z")

</div>

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