Elasticsearch: Ingest timestamp is not parseable as a valid ES date

Created on 14 Feb 2017  路  1Comment  路  Source: elastic/elasticsearch

To repro:

Create an index with a field 'timestamp' set to date type.
Create the following ingest pipeline:

PUT _ingest/pipeline/timestamp 
{ 
"description" : "Adds a timestamp field at the current time", 
"processors" : [ { 
"set" : { 
"field": "timestamp", 
"value": "{{_ingest.timestamp}}" 
} 
} ] 
} 

Attempt to ingest a document using this pipeline.

Result:

{
  "error": {
    "root_cause": [
      {
        "type": "mapper_parsing_exception",
        "reason": "failed to parse [timestamp]"
      }
    ],
    "type": "mapper_parsing_exception",
    "reason": "failed to parse [timestamp]",
    "caused_by": {
      "type": "illegal_argument_exception",
      "reason": "Invalid format: \"Tue Feb 14 12:49:00 EST 2017\""
    }
  },
  "status": 400
}

This is specifically the method described in the documentation as a possible replacement for _timestamp. We can work around it with a date processor in the ingest pipeline, but that's a really clunky solution for users trying to get the _timestamp feature back.

:CorFeatureIngest >bug v5.2.0

Most helpful comment

>All comments

Was this page helpful?
0 / 5 - 0 ratings