@clintongormley I know Beats requested this feature a while back... I was not aware that an empty string _index results in a successful non-index?

One way to achieve this is to run a fail processor. The difference here is that we would not return back a 2XX for this request, and the client would think there was a problem, instead of "dropping was successful".

Would ES need to change to support this? I tried indexing a document with an empty _index and get this:

{
  "took": 0,
  "errors": true,
  "items": [
    {
      "index": {
        "_index": "",
        "_type": "type",
        "_id": "id",
        "status": 500,
        "error": {
          "type": "string_index_out_of_bounds_exception",
          "reason": "String index out of range: 0"
        }
      }
    }
  ]
}

maybe if we introduce a new status for index items that are intended to be dropped? Maybe the pipeline can update metadata that will follow-up with an index request with a drop flag? since we would have to return a response to the user about this operation so the items array aligns with the request body

and respond with:

{
  "took": 884,
  "errors": false,
  "items": [
    {
      "index": {
        "_index": "",
        "_type": "type",
        "_id": "id",
        "_version": 1,
        "result": "dropped",
        "created": false,
        "status": 200
      }
    }
  ]
}

Drop document in ingest pipeline #23726

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions