你如何编写NEST代码来为这个简单的布尔逻辑生成弹性搜索查询?
term1 && (term2 || term3 || term4)
我使用Nest(5.2)语句执行此逻辑的伪代码查询ElasticSearch(5.2)
// additional requirements
( truckOemName = "HYSTER" && truckModelName = "S40FT" && partCategoryCode = "RECO" && partID != "")
//Section I can't get working correctly
AND (
( SerialRangeInclusiveFrom <= "F187V-6785D" AND SerialRangeInclusiveTo >= "F187V-6060D" )
OR
( SerialRangeInclusiveFrom = "" || SerialRangeInclusiveTo = "" )
)
Writing Bool Queries中的“将查询与||或应该是条款组合”提及
bool
查询并不完全遵循您对编程语言所期望的相同布尔逻辑。term1 && (term2 || term3 || term4)
没有成为
bool
|___must
| |___term1
|
|___should
|___term2
|___term3
|___term4
你可以找回只包含term1的结果
这正是我认为正在发生的事情。
但他们解决这个问题的答案超出了我对如何将其应用于Nest的理解。答案是?
- 添加括号以强制评估订单(我)
- 使用
boost
因子? (什么?)
这是NEST代码
var searchDescriptor = new SearchDescriptor<ElasticPart>();
var terms = new List<Func<QueryContainerDescriptor<ElasticPart>, QueryContainer>>
{
s =>
(s.TermRange(r => r.Field(f => f.SerialRangeInclusiveFrom)
.LessThanOrEquals(dataSearchParameters.SerialRangeEnd))
&&
s.TermRange(r => r.Field(f => f.SerialRangeInclusiveTo)
.GreaterThanOrEquals(dataSearchParameters.SerialRangeStart)))
//None of the data that matches these ORs returns with the query this code generates, below.
||
(!s.Exists(exists => exists.Field(f => f.SerialRangeInclusiveFrom))
||
!s.Exists(exists => exists.Field(f => f.SerialRangeInclusiveTo))
)
};
//Terms is the piece in question
searchDescriptor.Query(s => s.Bool(bq => bq.Filter(terms))
&& !s.Terms(term => term.Field(x => x.OemID)
.Terms(RulesHelper.GetOemExclusionList(exclusions))));
searchDescriptor.Aggregations(a => a
.Terms(aggPartInformation, t => t.Script(s => s.Inline(script)).Size(50000))
);
searchDescriptor.Type(string.Empty);
searchDescriptor.Size(0);
var searchResponse = ElasticClient.Search<ElasticPart>(searchDescriptor);
这是它生成的ES JSON查询
{
"query":{
"bool":{
"must":[
{
"term":{ "truckOemName": { "value":"HYSTER" }}
},
{
"term":{ "truckModelName": { "value":"S40FT" }}
},
{
"term":{ "partCategoryCode": { "value":"RECO" }}
},
{
"bool":{
"should":[
{
"bool":{
"must":[
{
"range":{ "serialRangeInclusiveFrom": { "lte":"F187V-6785D" }}
},
{
"range":{ "serialRangeInclusiveTo": { "gte":"F187V-6060D" }}
}
]
}
},
{
"bool":{
"must_not":[
{
"exists":{ "field":"serialRangeInclusiveFrom" }
}
]
}
},
{
"bool":{
"must_not":[
{
"exists":{ "field":"serialRangeInclusiveTo" }
}
]
}
}
]
}
},
{
"exists":{
"field":"partID"
}
}
]
}
}
}
这是我们希望它生成的查询似乎有效。
{
"query": {
"bool": {
"must": [
{
"bool": {
"must": [
{
"term": { "truckOemName": { "value": "HYSTER" }}
},
{
"term": {"truckModelName": { "value": "S40FT" }}
},
{
"term": {"partCategoryCode": { "value": "RECO" }}
},
{
"exists": { "field": "partID" }
}
],
"should": [
{
"bool": {
"must": [
{
"range": { "serialRangeInclusiveFrom": {"lte": "F187V-6785D"}}
},
{
"range": {"serialRangeInclusiveTo": {"gte": "F187V-6060D"}}
}
]
}
},
{
"bool": {
"must_not": [
{
"exists": {"field": "serialRangeInclusiveFrom"}
},
{
"exists": { "field": "serialRangeInclusiveTo"}
}
]
}
}
]
}
}
]
}
}
}
对于bool
查询的重载运算符,无法表达与must
子句结合的should
子句,即
term1 && (term2 || term3 || term4)
变
bool
|___must
|___term1
|___bool
|___should
|___term2
|___term3
|___term4
这是一个带有两个bool
子句的must
查询,其中第二个must
子句是bool
查询,其中必须匹配至少一个should
子句。 NEST结合了这样的查询,因为它符合.NET中布尔逻辑的期望。
如果确实成了
bool
|___must
| |___term1
|
|___should
|___term2
|___term3
|___term4
如果文档仅满足must
条款,则认为该文档是匹配的。在这种情况下,should
条款起到提升的作用,即如果文档与should
子句中的一个或多个must
子句匹配,那么它将具有更高的相关性得分,假设term2
,term3
和term4
是计算a的查询相关性得分。
在此基础上,您要生成的查询表示,对于要视为匹配的文档,它必须匹配must
子句中的所有4个查询
"must": [
{
"term": { "truckOemName": { "value": "HYSTER" }}
},
{
"term": {"truckModelName": { "value": "S40FT" }}
},
{
"term": {"partCategoryCode": { "value": "RECO" }}
},
{
"exists": { "field": "partID" }
}
],
那么,对于匹配must
条款的文件,如果
serialRangeInclusiveFrom
的"F187V-6785D"
和一个大于或等于serialRangeInclusiveFrom
的"F187V-6060D"
要么serialRangeInclusiveFrom
和serialRangeInclusiveTo
然后提高文档相关性得分。关键的一点是
如果文档与
must
子句匹配但与should
子句中的任何一个都不匹配,则它仍然是查询的匹配项(但具有较低的相关性分数)。
如果这是意图,则可以构造此查询using the longer form of the Bool
query