-
Type:
Improvement
-
Status: Open
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 2021.17
-
Component/s: Elasticsearch
-
Tags:
-
Backlog priority:600
-
Team:PLATFORM
NXP-30878 has added the support for the "max_expansions" property when building a query for the LIKE operator. But it does not cover the case when a MatchPhrasePrefixQueryBuilder object is built from a hint, as with the DEFAULT_DOCUMENT_SUGGESTION provider
<coreQueryPageProvider name="DEFAULT_DOCUMENT_SUGGESTION">
<property name="maxResults">PAGE_SIZE</property>
<pattern quoteParameters="false" escapeParameters="true">
SELECT * FROM Document WHERE /*+ES: INDEX(dc:title.fulltext) OPERATOR(match_phrase_prefix) */ ecm:fulltext.dc:title LIKE '?' AND ecm:mixinType !=
'HiddenInNavigation' AND ecm:isVersion = 0 AND
ecm:isTrashed = 0 AND ecm:parentId IS NOT NULL
</pattern>
<pageSize>10</pageSize>
</coreQueryPageProvider>
Expected behavior: the custom max_expansions value is set for any case where the match_phrase_prefix operator is used
