recency boost on meta engines excludes all engines which does not contain the property. Is this a desired behavior? This can lead to misleading search results if this behavior is not known.
Elastic Version v8.8.2 was used in an Elastic Cloud deployment.
Hi CodeDan, this is indeed a bug and not the desired behaviour. There is a workaround, however.
If you index a dummy document with a valid value for the boosted field into every source engine, then the recency boost on the meta engine will no longer exclude any source engines. You can delete the dummy file afterwards as well.
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.