Hello, I just upgraded from version 1.4.4 to 2.3.3 and I'm having an issue with the percolator: Before, we used to send the percolator requests using the _mpercolate endpoint for an existing document as follows: curl -XGET 'localhost:9200/_mpercolate' -d ' {"percolate":{"id":"myid_123456","index":…

Apologies for the late response. The reason for this error is that the author field is not mapped in the percolator index. Adding the field to the percolate index should fix this. Unfortunately there is a difference between how percolating an existing document and percolating a provided document …

Discuss the Elastic Stack

Percolator throws INTERNAL_SERVER_ERROR on irrelevant field

Elastic Stack Elasticsearch

Topic		Replies	Views
Problem creating percolator - No field mapping can be found for the field with name Elasticsearch	3	3137	July 5, 2017
Error Creating Percolator Elasticsearch	9	377	July 6, 2017
Heisenbug with Percolator Elasticsearch	3	369	July 6, 2017
Notice: Percolate failure when using same field name with several values Elasticsearch	1	279	July 6, 2017
Percolator filtering not working? Elasticsearch	6	662	July 6, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Percolator throws INTERNAL_SERVER_ERROR on irrelevant field

Related topics