Known issuesedit
The following known issues affect App Search.
-
The Generate Search Experience functionality does not work with traffic filters.
Use the following workaround:
- Clone Search UI repo (React library used to generate the search experience).
-
Rename
engine.json.exampletoengine.json. -
Update
engine.jsonto point the React app to your Enterprise Search endpoint. -
Update
engine.jsonto reference your engine’s fields (if not using the samplenational-parksengine). - Follow the getting started documentation to run the app.
-
App Search users with dev and editor roles do not have access to the App Search web crawler.
This applies to all versions of App Search.
-
App Search may return unexpected results when using Lucene Boolean search syntax (e.g.
<term> OR <other-term>)App Search’s relevance tuning can cause logical conflicts with queries that attempt to use Lucene’s Boolean query syntax. This is due to how the underlying Elasticsearch query is crafted for certain relevance tuning settings.
A workaround is to use the Elasticsearch search API to construct an Elasticsearch DSL request with Boolean logic to App Search.
-
Multi word synonyms are not used in a phrase match, but matched as individual words.
It is possible for a document that contains the multi word synonym to rank lower than another document that contains the individual terms in a different order.