是否可以从 Azure 搜索中获取类似 Solr 的调试信息?
Is it possible to get Solr-like debug information from Azure Search?
是否可以获得有关 returned 结果的详细信息以及如何以及为什么对它们进行评分? Solr 有一个调试选项,您可以在其中准确查看给定文档的评分方式,还可以 return 查询的解释计划。
我一直在搜索 Azure 搜索文档,但我没有看到其中提到的任何内容。
Azure 搜索中是否有任何类型的调试功能,如果没有,此服务的路线图上是否有任何此类功能?
更新:补充说明,希望得到回复:
例如,这是一个由查询 return 编辑的文档的调试信息示例:
"2122aaea-dac2-4934-b6d2-5f38bdc906de": {
"match": true,
"value": 1.1052036,
"description": "weight(_text_:house in 7) [SchemaSimilarity], result of:",
"details": [
{
"match": true,
"value": 1.1052036,
"description": "score(freq=2.0), product of:",
"details": [
{
"match": true,
"value": 1.8216125,
"description": "idf, computed as log(1 + (N - n + 0.5) / (n + 0.5)) from:",
"details": [
{
"match": true,
"value": 5,
"description": "n, number of documents containing term"
},
{
"match": true,
"value": 33,
"description": "N, total number of documents with field"
}
]
},
{
"match": true,
"value": 0.6067172,
"description": "tf, computed as freq / (freq + k1 * (1 - b + b * dl / avgdl)) from:",
"details": [
{
"match": true,
"value": 2.0,
"description": "freq, occurrences of term within document"
},
{
"match": true,
"value": 1.2,
"description": "k1, term saturation parameter"
},
{
"match": true,
"value": 0.75,
"description": "b, length normalization parameter"
},
{
"match": true,
"value": 248.0,
"description": "dl, length of field (approximate)"
},
{
"match": true,
"value": 224.0,
"description": "avgdl, average length of field"
}
]
}
]
}
]
}
此刻的答案是否定的。不幸的是,没有可用的 "debug" / "explain" 功能,但由于这是一个常见的请求,如果他们将来添加它,我不会感到惊讶。
是否可以获得有关 returned 结果的详细信息以及如何以及为什么对它们进行评分? Solr 有一个调试选项,您可以在其中准确查看给定文档的评分方式,还可以 return 查询的解释计划。
我一直在搜索 Azure 搜索文档,但我没有看到其中提到的任何内容。
Azure 搜索中是否有任何类型的调试功能,如果没有,此服务的路线图上是否有任何此类功能?
更新:补充说明,希望得到回复:
例如,这是一个由查询 return 编辑的文档的调试信息示例:
"2122aaea-dac2-4934-b6d2-5f38bdc906de": {
"match": true,
"value": 1.1052036,
"description": "weight(_text_:house in 7) [SchemaSimilarity], result of:",
"details": [
{
"match": true,
"value": 1.1052036,
"description": "score(freq=2.0), product of:",
"details": [
{
"match": true,
"value": 1.8216125,
"description": "idf, computed as log(1 + (N - n + 0.5) / (n + 0.5)) from:",
"details": [
{
"match": true,
"value": 5,
"description": "n, number of documents containing term"
},
{
"match": true,
"value": 33,
"description": "N, total number of documents with field"
}
]
},
{
"match": true,
"value": 0.6067172,
"description": "tf, computed as freq / (freq + k1 * (1 - b + b * dl / avgdl)) from:",
"details": [
{
"match": true,
"value": 2.0,
"description": "freq, occurrences of term within document"
},
{
"match": true,
"value": 1.2,
"description": "k1, term saturation parameter"
},
{
"match": true,
"value": 0.75,
"description": "b, length normalization parameter"
},
{
"match": true,
"value": 248.0,
"description": "dl, length of field (approximate)"
},
{
"match": true,
"value": 224.0,
"description": "avgdl, average length of field"
}
]
}
]
}
]
}
此刻的答案是否定的。不幸的是,没有可用的 "debug" / "explain" 功能,但由于这是一个常见的请求,如果他们将来添加它,我不会感到惊讶。