Adjustments to Relevance Tuning for a single Engine: Search settings are controllable from the query side consider passing Search Fields query parameters instead.via browser language settings or language detection - and direct the query to the correct Engine. If you do have different Engines for each language, a much more effective pattern is to identify the language - e.g. A way to avoid identifying search language: If you have the same content in multiple languages, indexing all of them using the Universal language choice works well.Remember that more fields results in slower queries. The best search results appear after condensing fields to just the essentials within one Engine. Large amounts of fields: Meta Engines aren't a way to expand the number of fields for a single set of documents.Here are some examples where Meta Engines are not the right solution: Meta Engines are useful but there are many other cases where a single Engine is a better choice. Remember, anyone with access to a Meta Engine has read access to all the Source Engines attached to it. Permissions also come into play - one unit might not want other units to be able to write new documents into their Engine, for example. Meta Engines allow both to exist together with a single engine-source-of-truth. They still need to be part of a company-wide search experience, and organization-wide search priorities that require Curations or Relevance Tunings that differ from specific business-unit needs. They enable comprehensive search over a collection of documents that have subsets with different search setting requirements.įor example, search experiences in large organizations often require documents from multiple business units, with standalone sites with Relevance Tunings specific to their needs. Meta Engines allow users to create a document-less Engine that searches over a set of existing Engines, with search settings that are separate from those Source Engines. "id": "western-national-parks|park_yosemite",
"id": "eastern-national-parks|park_shenandoah", The Engines that comprise a Meta Engine are referred to as Source Engines.Įxample: Two Engines, "western-national-parks" and "eastern-national-parks" can be combined in a Meta Engine named "parks" so that they can be searched as one data-set. Instead, it combines multiple other Engines so that they can be searched together as if they were a single Engine. What is a Meta EngineĪ Meta Engine is an Engine that has no Documents of its own. NOTE: Meta Engines are only available in the Elastic Cloud and Self-Managed version of App Search, with a Platinum License.
0 kommentar(er)
