Date index name processor

The purpose of this processor is to point documents to the right time based index based on a date or timestamp field in a document by using the date math index name support.

The processor sets the _index metadata field with a date math index name expression based on the provided index name prefix, a date or timestamp field in the documents being processed and the provided date rounding.

First, this processor fetches the date or timestamp from a field in the document being processed. Optionally, date formatting can be configured on how the field’s value should be parsed into a date. Then this date, the provided index name prefix and the provided date rounding get formatted into a date math index name expression. Also here optionally date formatting can be specified on how the date should be formatted into a date math index name expression.

An example pipeline that points documents to a monthly index that starts with a my-index- prefix based on a date in the date1 field:

  1. PUT _ingest/pipeline/monthlyindex
  2. {
  3. "description": "monthly date-time index naming",
  4. "processors" : [
  5. {
  6. "date_index_name" : {
  7. "field" : "date1",
  8. "index_name_prefix" : "my-index-",
  9. "date_rounding" : "M"
  10. }
  11. }
  12. ]
  13. }

Using that pipeline for an index request:

  1. PUT /my-index/_doc/1?pipeline=monthlyindex
  2. {
  3. "date1" : "2016-04-25T12:02:01.789Z"
  4. }
  1. {
  2. "_index" : "my-index-2016-04-01",
  3. "_type" : "_doc",
  4. "_id" : "1",
  5. "_version" : 1,
  6. "result" : "created",
  7. "_shards" : {
  8. "total" : 2,
  9. "successful" : 1,
  10. "failed" : 0
  11. },
  12. "_seq_no" : 55,
  13. "_primary_term" : 1
  14. }

The above request will not index this document into the my-index index, but into the my-index-2016-04-01 index because it was rounded by month. This is because the date-index-name-processor overrides the _index property of the document.

To see the date-math value of the index supplied in the actual index request which resulted in the above document being indexed into my-index-2016-04-01 we can inspect the effects of the processor using a simulate request.

  1. POST _ingest/pipeline/_simulate
  2. {
  3. "pipeline" :
  4. {
  5. "description": "monthly date-time index naming",
  6. "processors" : [
  7. {
  8. "date_index_name" : {
  9. "field" : "date1",
  10. "index_name_prefix" : "my-index-",
  11. "date_rounding" : "M"
  12. }
  13. }
  14. ]
  15. },
  16. "docs": [
  17. {
  18. "_source": {
  19. "date1": "2016-04-25T12:02:01.789Z"
  20. }
  21. }
  22. ]
  23. }

and the result:

  1. {
  2. "docs" : [
  3. {
  4. "doc" : {
  5. "_id" : "_id",
  6. "_index" : "<my-index-{2016-04-25||/M{yyyy-MM-dd|UTC}}>",
  7. "_type" : "_doc",
  8. "_source" : {
  9. "date1" : "2016-04-25T12:02:01.789Z"
  10. },
  11. "_ingest" : {
  12. "timestamp" : "2016-11-08T19:43:03.850+0000"
  13. }
  14. }
  15. }
  16. ]
  17. }

The above example shows that _index was set to <my-index-{2016-04-25||/M{yyyy-MM-dd|UTC}}>. Elasticsearch understands this to mean 2016-04-01 as is explained in the date math index name documentation

Table 10. Date index name options

NameRequiredDefaultDescription

field

yes

-

The field to get the date or timestamp from.

index_name_prefix

no

-

A prefix of the index name to be prepended before the printed date. Supports template snippets.

date_rounding

yes

-

How to round the date when formatting the date into the index name. Valid values are: y (year), M (month), w (week), d (day), h (hour), m (minute) and s (second). Supports template snippets.

date_formats

no

yyyy-MM-dd’T’HH:mm:ss.SSSXX

An array of the expected date formats for parsing dates / timestamps in the document being preprocessed. Can be a java time pattern or one of the following formats: ISO8601, UNIX, UNIX_MS, or TAI64N.

timezone

no

UTC

The timezone to use when parsing the date and when date math index supports resolves expressions into concrete index names.

locale

no

ENGLISH

The locale to use when parsing the date from the document being preprocessed, relevant when parsing month names or week days.

index_name_format

no

yyyy-MM-dd

The format to be used when printing the parsed date into the index name. A valid java time pattern is expected here. Supports template snippets.

if

no

-

Conditionally execute this processor.

on_failure

no

-

Handle failures for this processor. See Handling Failures in Pipelines.

ignore_failure

no

false

Ignore failures for this processor. See Handling Failures in Pipelines.

tag

no

-

An identifier for this processor. Useful for debugging and metrics.