[NXP-30878] Add property to set max_expansion on match_phrase_prefix operator - Nuxeo Issue Tracker

XML

Word

Printable

Details

Type: Improvement
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: 10.10
Fix Version/s: 10.10-HF59, 2021.17
Component/s: Elasticsearch

Release Notes Summary:
max_expansion on match_phrase_prefix is set with the property "elastic.max_expansions".
Tags:
- SupCom
- nxsupport
Backlog priority:
400
Upgrade notes:
Hide

Max expansions can be configured through the Configuration service with a contribution like

<extension target="org.nuxeo.runtime.ConfigurationService" point="configuration"> <property name="elasticsearch.max_expansions">200</property> </extension>
Show
Max expansions can be configured through the Configuration service with a contribution like <extension target= "org.nuxeo.runtime.ConfigurationService" point= "configuration" > <property name= "elasticsearch.max_expansions" > 200 </property> </extension>
Sprint:
nxsupport 15

Description

match_phrase_prefix query used for autocompletion can sometimes produce confusing results because it takes only 50 (default max_expansion) terms from the dictionary which may hides some results.

Exposing a property to set a custom value for this ES parameter would help to solve customers' issues

Attachments

Issue Links

is related to

NXP-31386 Find a solution to bypass the limitation to 50 results when using LIKE/ILIKE operators

Resolved

Activity

People

Assignee:

Thierry Martins

Reporter:

Thierry Martins

Participants:

Jenkins, Support Tech User, Thierry Martins

Votes:

0 Vote for this issue

Watchers:

3 Start watching this issue

Dates

Created:

2022-02-15 16:28

Updated:

2022-11-15 15:09

Resolved:

2022-02-21 18:17

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

1h 30m