Azure搜索得分 [英] Azure Search scoring
问题描述
我在Azure搜索中有3个相同的(以文本形式)项目集，这些项目因价格和积分而异.具有较高积分的廉价产品将获得更高的提升. (价格比点数提高得更多，反之亦然).
I have sets of 3 identical (in Text) items in Azure Search varying on Price and Points. Cheaper products with higher points are boosted higher. (Price is boosted more then Points, and is boosted inversely).
但是，我一直看到与此类似的搜索结果.
However, I keep seeing search results similar to this.
搜索位于约翰·米尔顿"上.
Search is on ‘john milton’.
我知道
Product="Id = 2-462109171829-1, Price=116.57, Points= 7, Name=Life of Schamyl / John Milton Mackie, Description=.", Score=32.499783
Product="Id = 2-462109171829-2, Price=116.40, Points= 9, Name=Life of Schamyl / John Milton Mackie, Description=.", Score=32.454872
Product="Id = 2-462109171829-3, Price=115.64, Points= 9, Name=Life of Schamyl / John Milton Mackie, Description=.", Score=32.316270
我希望评分顺序是这样的，价格最低的先行.
I expect the scoring order to be something like this, with the lowest price first.
Product="Id = 2-462109171829-3, Price=115.64, Points= 9, Name=Life of Schamyl / John Milton Mackie, Description=.", Score=
Product="Id = 2-462109171829-2, Price=116.40, Points= 9, Name=Life of Schamyl / John Milton Mackie, Description=.", Score=
Product="Id = 2-462109171829-1, Price=116.57, Points= 7, Name=Life of Schamyl / John Milton Mackie, Description=.", Score=
我缺少什么或可接受小的计分方式?
What am I missing or are minor scoring variations acceptable?
索引定义为
let ProductDataIndex =
let fields =
[|
new Field (
"id",
DataType.String,
IsKey = true,
IsSearchable = true);
new Field (
"culture",
DataType.String,
IsSearchable = true);
new Field (
"gran",
DataType.String,
IsSearchable = true);
new Field (
"name",
DataType.String,
IsSearchable = true);
new Field (
"description",
DataType.String,
IsSearchable = true);
new Field (
"price",
DataType.Double,
IsSortable = true,
IsFilterable = true)
new Field (
"points",
DataType.Int32,
IsSortable = true,
IsFilterable = true)
|]
let weightsText =
new TextWeights(
Weights = ([|
("name", 4.);
("description", 2.)
|]
|> dict))
let priceBoost =
new MagnitudeScoringFunction(
new MagnitudeScoringParameters(
BoostingRangeStart = 1000.0,
BoostingRangeEnd = 0.0,
ShouldBoostBeyondRangeByConstant = true),
"price",
10.0)
let pointsBoost =
new MagnitudeScoringFunction(
new MagnitudeScoringParameters(
BoostingRangeStart = 0.0,
BoostingRangeEnd = 10000000.0,
ShouldBoostBeyondRangeByConstant = true),
"points",
2.0)
let scoringProfileMain =
new ScoringProfile (
"main",
TextWeights =
weightsText,
Functions =
new List<ScoringFunction>(
[
priceBoost :> ScoringFunction
pointsBoost :> ScoringFunction
]),
FunctionAggregation =
ScoringFunctionAggregation.Sum)
new Index
(Name = ProductIndexName
,Fields = fields
,ScoringProfiles = new List<ScoringProfile>(
[
scoringProfileMain
]))
推荐答案
Azure搜索中的所有索引均被拆分为多个分片，从而使我们能够快速扩展和缩小.发出搜索请求后，将针对每个分片单独发出搜索请求.然后，将每个分片的结果集合并并按分数排序(如果未定义其他排序). 重要的是要知道，评分函数对每个文档中的查询词频度与分片中所有文档的频度进行加权！
All indexes in Azure Search are split into multiple shards allowing us for quick scale up and scale downs. When a search request is issued, it’s issued against each of the shards independently. The result sets from each of the shards are then merged and ordered by score (if no other ordering is defined). It is important to know that the scoring function weights query term frequency in each document against its frequency in all documents, in the shard!
这意味着在您的方案中，每个文档有三个实例，即使禁用了评分配置文件，如果其中一个文档位于与其他两个文档不同的分片上，其得分也会略有不同.索引中的数据越多，差异将越小(术语分布越均匀).无法假定任何给定文档将放置在哪个分片上.
It means that in your scenario, in which you have three instances of every document, even with scoring profiles disabled, if one of those documents lands on a different shard than the other two, its score will be slightly different. The more data in your index, the smaller the differences will be (more even term distribution). It’s not possible to assume on which shard any given document will be placed.
通常，文档分数不是订购文档的最佳属性.它只应使您对结果集中的文档与其他文档具有相关性的一般认识.在您的方案中，如果您将价格和/或积分字段标记为可排序，则可以按价格和/或积分对结果进行排序.您可以在此处找到有关如何使用$ orderby查询参数的更多信息: https://msdn.microsoft.com/zh-CN/library/azure/dn798927.aspx
In general, document score is not the best attribute for ordering documents. It should only give you general sense of document relevance against other documents in the results set. In your scenario, it would be possible to order the results by price and/or points if you marked price and/or points fields as sortable. You can find more information how to use $orderby query parameter here: https://msdn.microsoft.com/en-us/library/azure/dn798927.aspx
这篇关于Azure搜索得分的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
