You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
var tmpQ = Query.Bool(b => b
.MinimumNumberShouldMatch(1)
.Should(
s1 => s1
.Match(qs1 => qs1.AnalyzerNullable(searchAnalyzer)
.OnField(manuField).Operator(Operator.and).QueryString(Name)
),
s2 => s2
.Match(qs2 => qs2.AnalyzerNullable(searchAnalyzer)
.OnField(manuAliasField).Operator(Operator.and).QueryString(Name)
),
s3 => s3
.Match(qs3 => qs3.AnalyzerNullable(searchAnalyzer)
.OnField(manuParentField).Operator(Operator.and).QueryString(Name)
)
)
);
The searchAnalyzer can be null because of some outside logic, currently I have to write an extension AnalyzerNullable to allow null for this.
I saw that the lib allow passing NULL to Analyzer() for QueryStringDescriptor, why not for MatchQueryDescriptor?
It's very handy since we dont have to do an IF THEN ELSE to build a query that has analyzer or not.
The text was updated successfully, but these errors were encountered: