Mixing
Azure Search Explain function
0
I'm trying to understand how the scoring has been generated for Azure Search matches as some of my results are distinctly odd (though probably correct if only I understood why!). There is nothing officially documented but is there anything like Lucene Explain for Azure Search?
Thanks
azure-search
asked Nov 19 '18 at 14:41
GrahamB
456721
add a comment |
0
I'm trying to understand how the scoring has been generated for Azure Search matches as some of my results are distinctly odd (though probably correct if only I understood why!). There is nothing officially documented but is there anything like Lucene Explain for Azure Search?
Thanks
azure-search
asked Nov 19 '18 at 14:41
GrahamB
456721
add a comment |
0
0
0
I'm trying to understand how the scoring has been generated for Azure Search matches as some of my results are distinctly odd (though probably correct if only I understood why!). There is nothing officially documented but is there anything like Lucene Explain for Azure Search?
Thanks
azure-search
asked Nov 19 '18 at 14:41
GrahamB
456721
I'm trying to understand how the scoring has been generated for Azure Search matches as some of my results are distinctly odd (though probably correct if only I understood why!). There is nothing officially documented but is there anything like Lucene Explain for Azure Search?
Thanks
azure-search
azure-search
asked Nov 19 '18 at 14:41
GrahamB
456721
asked Nov 19 '18 at 14:41
GrahamB
456721
asked Nov 19 '18 at 14:41
GrahamB
456721
asked Nov 19 '18 at 14:41
GrahamB
456721
asked Nov 19 '18 at 14:41
GrahamB
456721
456721
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
0
The default scoring method use the TF-IDF algorithm to calculate a value for each searchable field in the document. Those values are then summed up together to create a final score.
More details on TFIDF here: https://lucene.apache.org/core/4_0_0/core/org/apache/lucene/search/similarities/TFIDFSimilarity.html
You can alter the score further by using scoring profiles to boost the score of certain fields.
https://docs.microsoft.com/en-us/rest/api/searchservice/add-scoring-profiles-to-a-search-index
answered Nov 20 '18 at 1:27
ramero-MSFT
863
Thanks ramero but that doesn't really help. I understand scoring profiles and vaguely understand TF-IDF but I'm getting relevancy scores that I don't understand why.... and my customers are asking why too as it looks like a bug to them. It would be helpful if I could ask Azure Search why it's rated something the way it has, similar to Lucene
– GrahamB
Nov 20 '18 at 13:40
Unfortunately, as of today, we do not expose an "explain" API. You can vote for the following suggestion to help us prioritize the work in the future: feedback.azure.com/forums/263029-azure-search/suggestions/… In the mean time, if you give us more details on your scenario and the results you are getting, we can try to help you further understand the score. If you don't feel comfortable sharing that information on stack overflow, feel free to send us an email directly at azscustquestions at microsoft dot com
– ramero-MSFT
Nov 21 '18 at 0:29
Thanks ramero - I'll see what I can pull out but really I need the ability to check myself as it could be one of many oddities. As for User Voice... nothing against you but don't get me started, that's a place where ideas tend to go to die as they are on there for years with high votes and nothing ever gets done about them. This particular issue is < 100 votes whereas others are 1000+ and still not dealt with, so I'm not hopeful
– GrahamB
Nov 21 '18 at 10:51
@GrahamB, you're right. We've been slow addressing feedback regarding user-facing features as our focus has been mostly on improving reliability, performance, security, regional roll-out etc. We're working hard to address most pressing customer asks, like Complex Types and others from the top of UserVoice. Unfortunately, the Explain API is not on the roadmap for the next 6 months. Please reach out if we can help with anything in the meantime by improving documentation, samples etc. Users find this article useful: docs.microsoft.com/en-us/azure/search/…
– Yahnoosh
Nov 21 '18 at 15:55
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53376972%2fazure-search-explain-function%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
The default scoring method use the TF-IDF algorithm to calculate a value for each searchable field in the document. Those values are then summed up together to create a final score.
More details on TFIDF here: https://lucene.apache.org/core/4_0_0/core/org/apache/lucene/search/similarities/TFIDFSimilarity.html
You can alter the score further by using scoring profiles to boost the score of certain fields.
https://docs.microsoft.com/en-us/rest/api/searchservice/add-scoring-profiles-to-a-search-index
answered Nov 20 '18 at 1:27
ramero-MSFT
863
Thanks ramero but that doesn't really help. I understand scoring profiles and vaguely understand TF-IDF but I'm getting relevancy scores that I don't understand why.... and my customers are asking why too as it looks like a bug to them. It would be helpful if I could ask Azure Search why it's rated something the way it has, similar to Lucene
– GrahamB
Nov 20 '18 at 13:40
Unfortunately, as of today, we do not expose an "explain" API. You can vote for the following suggestion to help us prioritize the work in the future: feedback.azure.com/forums/263029-azure-search/suggestions/… In the mean time, if you give us more details on your scenario and the results you are getting, we can try to help you further understand the score. If you don't feel comfortable sharing that information on stack overflow, feel free to send us an email directly at azscustquestions at microsoft dot com
– ramero-MSFT
Nov 21 '18 at 0:29
Thanks ramero - I'll see what I can pull out but really I need the ability to check myself as it could be one of many oddities. As for User Voice... nothing against you but don't get me started, that's a place where ideas tend to go to die as they are on there for years with high votes and nothing ever gets done about them. This particular issue is < 100 votes whereas others are 1000+ and still not dealt with, so I'm not hopeful
– GrahamB
Nov 21 '18 at 10:51
@GrahamB, you're right. We've been slow addressing feedback regarding user-facing features as our focus has been mostly on improving reliability, performance, security, regional roll-out etc. We're working hard to address most pressing customer asks, like Complex Types and others from the top of UserVoice. Unfortunately, the Explain API is not on the roadmap for the next 6 months. Please reach out if we can help with anything in the meantime by improving documentation, samples etc. Users find this article useful: docs.microsoft.com/en-us/azure/search/…
– Yahnoosh
Nov 21 '18 at 15:55
add a comment |
0
The default scoring method use the TF-IDF algorithm to calculate a value for each searchable field in the document. Those values are then summed up together to create a final score.
More details on TFIDF here: https://lucene.apache.org/core/4_0_0/core/org/apache/lucene/search/similarities/TFIDFSimilarity.html
You can alter the score further by using scoring profiles to boost the score of certain fields.
https://docs.microsoft.com/en-us/rest/api/searchservice/add-scoring-profiles-to-a-search-index
answered Nov 20 '18 at 1:27
ramero-MSFT
863
Thanks ramero but that doesn't really help. I understand scoring profiles and vaguely understand TF-IDF but I'm getting relevancy scores that I don't understand why.... and my customers are asking why too as it looks like a bug to them. It would be helpful if I could ask Azure Search why it's rated something the way it has, similar to Lucene
– GrahamB
Nov 20 '18 at 13:40
Unfortunately, as of today, we do not expose an "explain" API. You can vote for the following suggestion to help us prioritize the work in the future: feedback.azure.com/forums/263029-azure-search/suggestions/… In the mean time, if you give us more details on your scenario and the results you are getting, we can try to help you further understand the score. If you don't feel comfortable sharing that information on stack overflow, feel free to send us an email directly at azscustquestions at microsoft dot com
– ramero-MSFT
Nov 21 '18 at 0:29
Thanks ramero - I'll see what I can pull out but really I need the ability to check myself as it could be one of many oddities. As for User Voice... nothing against you but don't get me started, that's a place where ideas tend to go to die as they are on there for years with high votes and nothing ever gets done about them. This particular issue is < 100 votes whereas others are 1000+ and still not dealt with, so I'm not hopeful
– GrahamB
Nov 21 '18 at 10:51
@GrahamB, you're right. We've been slow addressing feedback regarding user-facing features as our focus has been mostly on improving reliability, performance, security, regional roll-out etc. We're working hard to address most pressing customer asks, like Complex Types and others from the top of UserVoice. Unfortunately, the Explain API is not on the roadmap for the next 6 months. Please reach out if we can help with anything in the meantime by improving documentation, samples etc. Users find this article useful: docs.microsoft.com/en-us/azure/search/…
– Yahnoosh
Nov 21 '18 at 15:55
add a comment |
0
0
0
The default scoring method use the TF-IDF algorithm to calculate a value for each searchable field in the document. Those values are then summed up together to create a final score.
More details on TFIDF here: https://lucene.apache.org/core/4_0_0/core/org/apache/lucene/search/similarities/TFIDFSimilarity.html
You can alter the score further by using scoring profiles to boost the score of certain fields.
https://docs.microsoft.com/en-us/rest/api/searchservice/add-scoring-profiles-to-a-search-index
answered Nov 20 '18 at 1:27
ramero-MSFT
863
The default scoring method use the TF-IDF algorithm to calculate a value for each searchable field in the document. Those values are then summed up together to create a final score.
More details on TFIDF here: https://lucene.apache.org/core/4_0_0/core/org/apache/lucene/search/similarities/TFIDFSimilarity.html
You can alter the score further by using scoring profiles to boost the score of certain fields.
https://docs.microsoft.com/en-us/rest/api/searchservice/add-scoring-profiles-to-a-search-index
answered Nov 20 '18 at 1:27
ramero-MSFT
863
answered Nov 20 '18 at 1:27
ramero-MSFT
863
answered Nov 20 '18 at 1:27
ramero-MSFT
863
answered Nov 20 '18 at 1:27
ramero-MSFT
863
863
Thanks ramero but that doesn't really help. I understand scoring profiles and vaguely understand TF-IDF but I'm getting relevancy scores that I don't understand why.... and my customers are asking why too as it looks like a bug to them. It would be helpful if I could ask Azure Search why it's rated something the way it has, similar to Lucene
– GrahamB
Nov 20 '18 at 13:40
Unfortunately, as of today, we do not expose an "explain" API. You can vote for the following suggestion to help us prioritize the work in the future: feedback.azure.com/forums/263029-azure-search/suggestions/… In the mean time, if you give us more details on your scenario and the results you are getting, we can try to help you further understand the score. If you don't feel comfortable sharing that information on stack overflow, feel free to send us an email directly at azscustquestions at microsoft dot com
– ramero-MSFT
Nov 21 '18 at 0:29
Thanks ramero - I'll see what I can pull out but really I need the ability to check myself as it could be one of many oddities. As for User Voice... nothing against you but don't get me started, that's a place where ideas tend to go to die as they are on there for years with high votes and nothing ever gets done about them. This particular issue is < 100 votes whereas others are 1000+ and still not dealt with, so I'm not hopeful
– GrahamB
Nov 21 '18 at 10:51
@GrahamB, you're right. We've been slow addressing feedback regarding user-facing features as our focus has been mostly on improving reliability, performance, security, regional roll-out etc. We're working hard to address most pressing customer asks, like Complex Types and others from the top of UserVoice. Unfortunately, the Explain API is not on the roadmap for the next 6 months. Please reach out if we can help with anything in the meantime by improving documentation, samples etc. Users find this article useful: docs.microsoft.com/en-us/azure/search/…
– Yahnoosh
Nov 21 '18 at 15:55
add a comment |
Thanks ramero but that doesn't really help. I understand scoring profiles and vaguely understand TF-IDF but I'm getting relevancy scores that I don't understand why.... and my customers are asking why too as it looks like a bug to them. It would be helpful if I could ask Azure Search why it's rated something the way it has, similar to Lucene
– GrahamB
Nov 20 '18 at 13:40
Unfortunately, as of today, we do not expose an "explain" API. You can vote for the following suggestion to help us prioritize the work in the future: feedback.azure.com/forums/263029-azure-search/suggestions/… In the mean time, if you give us more details on your scenario and the results you are getting, we can try to help you further understand the score. If you don't feel comfortable sharing that information on stack overflow, feel free to send us an email directly at azscustquestions at microsoft dot com
– ramero-MSFT
Nov 21 '18 at 0:29
Thanks ramero - I'll see what I can pull out but really I need the ability to check myself as it could be one of many oddities. As for User Voice... nothing against you but don't get me started, that's a place where ideas tend to go to die as they are on there for years with high votes and nothing ever gets done about them. This particular issue is < 100 votes whereas others are 1000+ and still not dealt with, so I'm not hopeful
– GrahamB
Nov 21 '18 at 10:51
@GrahamB, you're right. We've been slow addressing feedback regarding user-facing features as our focus has been mostly on improving reliability, performance, security, regional roll-out etc. We're working hard to address most pressing customer asks, like Complex Types and others from the top of UserVoice. Unfortunately, the Explain API is not on the roadmap for the next 6 months. Please reach out if we can help with anything in the meantime by improving documentation, samples etc. Users find this article useful: docs.microsoft.com/en-us/azure/search/…
– Yahnoosh
Nov 21 '18 at 15:55
Thanks ramero but that doesn't really help. I understand scoring profiles and vaguely understand TF-IDF but I'm getting relevancy scores that I don't understand why.... and my customers are asking why too as it looks like a bug to them. It would be helpful if I could ask Azure Search why it's rated something the way it has, similar to Lucene
– GrahamB
Nov 20 '18 at 13:40
Thanks ramero but that doesn't really help. I understand scoring profiles and vaguely understand TF-IDF but I'm getting relevancy scores that I don't understand why.... and my customers are asking why too as it looks like a bug to them. It would be helpful if I could ask Azure Search why it's rated something the way it has, similar to Lucene
– GrahamB
Nov 20 '18 at 13:40
Unfortunately, as of today, we do not expose an "explain" API. You can vote for the following suggestion to help us prioritize the work in the future: feedback.azure.com/forums/263029-azure-search/suggestions/… In the mean time, if you give us more details on your scenario and the results you are getting, we can try to help you further understand the score. If you don't feel comfortable sharing that information on stack overflow, feel free to send us an email directly at azscustquestions at microsoft dot com
– ramero-MSFT
Nov 21 '18 at 0:29
Unfortunately, as of today, we do not expose an "explain" API. You can vote for the following suggestion to help us prioritize the work in the future: feedback.azure.com/forums/263029-azure-search/suggestions/… In the mean time, if you give us more details on your scenario and the results you are getting, we can try to help you further understand the score. If you don't feel comfortable sharing that information on stack overflow, feel free to send us an email directly at azscustquestions at microsoft dot com
– ramero-MSFT
Nov 21 '18 at 0:29
Thanks ramero - I'll see what I can pull out but really I need the ability to check myself as it could be one of many oddities. As for User Voice... nothing against you but don't get me started, that's a place where ideas tend to go to die as they are on there for years with high votes and nothing ever gets done about them. This particular issue is < 100 votes whereas others are 1000+ and still not dealt with, so I'm not hopeful
– GrahamB
Nov 21 '18 at 10:51
Thanks ramero - I'll see what I can pull out but really I need the ability to check myself as it could be one of many oddities. As for User Voice... nothing against you but don't get me started, that's a place where ideas tend to go to die as they are on there for years with high votes and nothing ever gets done about them. This particular issue is < 100 votes whereas others are 1000+ and still not dealt with, so I'm not hopeful
– GrahamB
Nov 21 '18 at 10:51
@GrahamB, you're right. We've been slow addressing feedback regarding user-facing features as our focus has been mostly on improving reliability, performance, security, regional roll-out etc. We're working hard to address most pressing customer asks, like Complex Types and others from the top of UserVoice. Unfortunately, the Explain API is not on the roadmap for the next 6 months. Please reach out if we can help with anything in the meantime by improving documentation, samples etc. Users find this article useful: docs.microsoft.com/en-us/azure/search/…
– Yahnoosh
Nov 21 '18 at 15:55
@GrahamB, you're right. We've been slow addressing feedback regarding user-facing features as our focus has been mostly on improving reliability, performance, security, regional roll-out etc. We're working hard to address most pressing customer asks, like Complex Types and others from the top of UserVoice. Unfortunately, the Explain API is not on the roadmap for the next 6 months. Please reach out if we can help with anything in the meantime by improving documentation, samples etc. Users find this article useful: docs.microsoft.com/en-us/azure/search/…
– Yahnoosh
Nov 21 '18 at 15:55
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53376972%2fazure-search-explain-function%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
