Hi, is there a specific reason, why the Match() query has operator set to and as a default when ElasticSearch sets it to or?
The default match query is of type boolean. It means that the text provided is analyzed and > the analysis process constructs a boolean query from the provided text. The operator flag > can be set to or or and to control the boolean clauses (defaults to or).
(http://www.elasticsearch.org/guide/reference/query-dsl/match-query/)
I'm going to leave it alone for now, since the resolution of #30 will take care of the issue (and prevent breaking what people are using in the mean time).
Hi, is there a specific reason, why the Match() query has operator set to and as a default when ElasticSearch sets it to or?