Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.8.0.Beta3
-
Fix Version/s: 5.8.0.Beta4
-
Component/s: elasticsearch
-
Labels:None
-
Bug Testcase Reminder (view):
-
Last commented by a user?:true
-
Pull Request:
Description
This seems to be caused by the fact we always include an "analyzer" parameter when building Elasticsearch phrase/match queries, and Elasticsearch won't understand when we pass a normalizer name in this parameter.
For instance:
private static JsonObject convertRemoteMatchQuery(RemoteMatchQuery query) { JsonObject matchQuery = JsonBuilder.object() .add( "match", JsonBuilder.object().add( query.getField(), JsonBuilder.object() .addProperty( "query", query.getSearchTerms() ) .addProperty( "analyzer", query.getAnalyzerReference().getAnalyzerName( query.getField() ) ) .append( fuzzinessAppender( query.getMaxEditDistance() ) ) .append( boostAppender( query ) ) ) ).build(); return wrapQueryForNestedIfRequired( query.getField(), matchQuery ); }
