SOLVED
Just minutes before the release of 5.0.0-alpha4
I found this bug.
I tried it in `5.0.0-alpha4' and it works fine. That's nice. But it still feels like I have lost some time...
I'm using elasticsearch-5.0.0-alpha3
and kibana-5.0.0-alpha3
.
Using Console I register a pipeline:
PUT _ingest/pipeline/x
{
"description": "Ingesting Meetup events",
"processors": [ ... ]
}
When I check if my pipeline exists:
GET _ingest/pipeline/x
It comes back the way it should:
{
"pipelines": [
{
"id": "x",
"config": {
"description": "x",
"processors": [ ... ]
}
}
]
}
But when I want to use it:
PUT a/b/c?pipeline=x
{
"z": 0
}
The response is:
{
"error": {
"root_cause": [
{
"type": "illegal_argument_exception",
"reason": "pipeline with id [x] does not exist"
}
],
"type": "illegal_argument_exception",
"reason": "pipeline with id [x] does not exist"
},
"status": 400
}
Also tried using curl
but I've got the same result.
Is there something I'm missing? Or is this a bug?