# Manual creation of an index with the date pattern name-YYYY.MM.DD

**URL:** <https://discuss.elastic.co/t/manual-creation-of-an-index-with-the-date-pattern-name-yyyy-mm-dd/128730>\
**Category:** Elasticsearch\
**Created:** [April 19, 2018, 2:46pm UTC](https://discuss.elastic.co/t/manual-creation-of-an-index-with-the-date-pattern-name-yyyy-mm-dd/128730 "2018-04-19T14:46:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [April 19, 2018, 3:06pm UTC](https://discuss.elastic.co/t/manual-creation-of-an-index-with-the-date-pattern-name-yyyy-mm-dd/128730/2 "2018-04-19T15:06:56Z")

</div>

Curator doesn't need to have a date stamp in the index name. You can use [`field_stats` based ages](https://www.elastic.co/guide/en/elasticsearch/client/curator/5.5/filtertype_age.html#_literal_field_stats_literal_based_ages) in Curator to identify the oldest and/or youngest `@timestamp` field in the index, removing the need to put a timestamp in the index name.

You're much better off using a default numeric rollover naming sequence to achieve this, with the aforementioned `field_stats` approach in Curator. But if you _must_ put a timestamp in your index name with a rollover approach, see [this forum post](https://discuss.elastic.co/t/how-can-i-name-curator-rollover-new-index-like-date-prefix-yyyy-mm-dd-1/128542/2?u=theuntergeek).

---

_[View the full topic](https://discuss.elastic.co/t/manual-creation-of-an-index-with-the-date-pattern-name-yyyy-mm-dd/128730)._