[FTS] queries should work when using the ngram and edge_ngram analyzers

Description

This relates to , during which it was discovered that doing match_phrase search on a field which had an analyzer that included the edge_ngram (back edge) did not work correctly.

Unfortunately, has also uncovered additional problems which should be resolved eventually. But, the more pressing issue is that we ensure that users who want to use ngrams, can do so without any complications.

This issue is thus broken out to focus on correcting this case.

Components

Affects versions

Fix versions

Labels

Environment

None

Link to Log File, atop/blg, CBCollectInfo, Core dump

None

Release Notes Description

None

Activity

MartyM May 31, 2017 at 7:04 PM

That should be all, I think we can close.

Aruna Piravi May 31, 2017 at 6:58 PM

Match phrase queries on an index that uses analyzers that contain ngram and edge_ngram now run successfully. The original test mentioned in does just that.

Please let me know if I need to add anything else. If not, let me close this issue. Thanks!

MartyM February 13, 2017 at 9:31 PM

Let me know if you need more input on what needs testing.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Is this a Regression?

Unknown

Triage

Untriaged

Priority

Instabug

Open Instabug

PagerDuty

Sentry

Zendesk Support

Created February 13, 2017 at 8:55 PM
Updated June 14, 2017 at 12:11 AM
Resolved February 13, 2017 at 9:31 PM
Instabug