azure-cognitive-search

问题 Does Azure Search support some way of ignoring accented characters? For example, if somebody searches for e it should include é characters in the search. Or would we need to add some converting at the moment of building the Azure Search Index? Any recomendations welcome, thanks. 回答1: Yes. Please use the ASCII folding analyzer on your field. To do that, set the analyzer property on your field to analyzer:"standardasciifolding.lucene" Alternatively, use a language specific analyzer e.g.

问题 Sometimes when using Azure Search's paging there may be duplicate documents in the results. Here is an example of a paging request: GET /indexes/myindex/docs?search=*$top=15&$skip=15&$orderby=rating desc Why is this possible? How can it happen? Are there any consistency guarantees when paging? 回答1: The results of paginated queries are not guaranteed to be stable if the underlying index is changing, or if you are relying on sorting by relevance score. Paging simply changes the value of $skip

问题 Reading the documentation for the Azure Search .NET SDK, I see that the ContinuationToken property is not supposed to used for pagination (this is the same as the @odata.nextLink and @search.nextPageParameter properties in the REST API). Note that this property is not meant to help you implement paging of search results. You can implement paging using the Top and Skip search parameters. Source Why can't I use it for pagination? I have a situation where I want to run a query and then step

问题 I have a question about a peculiar behavior I noticed in my custom analyzer (as well as in the fr.microsoft analyzer). The below Analyze API tests are shown using the “fr.microsoft” analyzer, but I saw the same exact behavior when I use my “text_contains_search_custom_analyzer” custom analyzer (which makes sense as I base it off the fr.microsoft analyzer). UAT reported that when they search for “femme” (singular) they expect documents with “femmes” (plural) to also be found. But when I tested

问题 I want to know how to filter and order the results by score with azure search. I tried : https://domaine.net/indexes/indexName/docs?search=TEST$orderby=@search.score%20desc&$count=true Return : object(stdClass)#322 (1) { ["error"]=> object(stdClass)#323 (2) { ["code"]=> string(0) "" ["message"]=> string(96) "Invalid expression: Syntax error at position 8 in '@search.score asc'. Parameter name: $orderby" } } 回答1: Results are sorted by score (descending) by default. If you sort by other

问题 a little relating and continuing to this question: Azure Search Analyzer I want to use a keywordanalyzer for word collections. We have documents (products) with different fields like product_name, brand, categorie and so on. To implement a keyword based ranking (scoring) I would like to add a Collection(Edm.String) field which contains different (untokenized!!) keywords, like: "brown teddy" or "green bean". To achieve this I thought about using a keywordanalyzer with the following definition:

问题 a little relating and continuing to this question: Azure Search Analyzer I want to use a keywordanalyzer for word collections. We have documents (products) with different fields like product_name, brand, categorie and so on. To implement a keyword based ranking (scoring) I would like to add a Collection(Edm.String) field which contains different (untokenized!!) keywords, like: "brown teddy" or "green bean". To achieve this I thought about using a keywordanalyzer with the following definition:

问题 After upgrading the .net Azure Search SDK to version 9, I am unable to search. The call just hangs on: azureSearchIndexClient.Documents.Search(query, parameters); I don't receive an error, everything was working on 5.0.3, I can still create, populate, and delete indexes in version 9. Without any response, I have little to go on... 回答1: This is a bug in version 9.0.0 of the SDK, tracked here: https://github.com/Azure/azure-sdk-for-net/issues/6254 It has since been fixed in version 9.0.1, now

问题 Scenario I'm building a suite of automated integration tests. Each test push data into the Azure Search index before querying it and verifying the expected results. Problem The indexation happens asynchronously in the service and data aren't immediatly available after the indexing call returns successfully. The test execute of course too rapidly most of the time. What I've tried I've tried querying the document until it's found: // Wait for the indexed document to become available while

问题 I am using hit-highlighting in azure search. It works fine but I want to fine tune it a bit. Say, a field has the following value: "It uses period as the delimiter. If not, please clarify" If I search for "please" I will get a highlight hit on that field, e.g.: "If not, <em> please </em> clarify" If I search for "period" I will get a highlight hit on that field, e.g.: "It uses <em> period </em> as the delimiter." After trying it with several examples it seems that it uses period (".") as a