azure-cognitive-search

问题 I'm trying to use synonym maps in Azure Search and i'm running into a problem. I want to have several words and phrases map into a single search query. In other words, when i search for either: product 123 , product0123 , product 0123 i want the search to return results for a query phrase: product123 . After reading the tutorial it all seemed pretty straight forward. I'm using .Net Azure.Search SDK 5.0 so i've done the following: var synonymMap = new SynonymMap { Name = "test-map", Format =

问题 I'm trying to use synonym maps in Azure Search and i'm running into a problem. I want to have several words and phrases map into a single search query. In other words, when i search for either: product 123 , product0123 , product 0123 i want the search to return results for a query phrase: product123 . After reading the tutorial it all seemed pretty straight forward. I'm using .Net Azure.Search SDK 5.0 so i've done the following: var synonymMap = new SynonymMap { Name = "test-map", Format =

问题 I'm trying to use synonym maps in Azure Search and i'm running into a problem. I want to have several words and phrases map into a single search query. In other words, when i search for either: product 123 , product0123 , product 0123 i want the search to return results for a query phrase: product123 . After reading the tutorial it all seemed pretty straight forward. I'm using .Net Azure.Search SDK 5.0 so i've done the following: var synonymMap = new SynonymMap { Name = "test-map", Format =

问题 According to this page, the default sort of Azure Search results is by Azure's own score (descending). However, you can supply an $orderby clause, which is defined as: A list of comma-separated expressions to sort the results by. Each expression can be either a field name or a call to the geo.distance() function. I want to sort by Azure's @search.score desc, MyFieldOne, MyFieldTwo. But, I cannot figure out how to reference the @search.score "field." I've tried the following: $orderby=search

问题 We have an issue with Azure Search Basic instances. tl;dr; is that OPTIONS pre-flight CORS request from browser gets a 403 FORBIDDEN in Search Basic. We resolved this by temporarily going to a Standard instance. We tried to create a Free service to test and develop a Search service for an Angular website, and we did so successfully. When we tried to upload the whole data set, it exceeded the quota, so we switched to a Basic tier. We updated the domain and key for the search, but it started to

问题 I'm using Azure Search based on the rich Lucene Query Parser syntax. I defined to "~1" as additional parameter to one symbol for distance ). But I faced with problem, that the entity is not ordered even if there is exact match. (For example,"blue~1" would return "blues", "blue", "glue". Or when searching product SKU like "P002", I would get result "P003", "P005", "P004", "P002", "P001", "P006" ) So my question: is there some way to define, that the entity with exact match must be first in

问题 I'm using Azure Search based on the rich Lucene Query Parser syntax. I defined to "~1" as additional parameter to one symbol for distance ). But I faced with problem, that the entity is not ordered even if there is exact match. (For example,"blue~1" would return "blues", "blue", "glue". Or when searching product SKU like "P002", I would get result "P003", "P005", "P004", "P002", "P001", "P006" ) So my question: is there some way to define, that the entity with exact match must be first in

问题 I thought I understood CORS, but there is something I do not understand apparently. I have an app that I am trying to run from localhost. This app needs to POST a request to Azure Search. I am trying to upload a search document. In an attempt to do this, I have the following: var url = 'https://my-app.search.windows.net/indexes/test/docs/index?api-version=2015-02-28'; $.ajax({ url: url, type: 'POST', contentType:'application/json', headers: { 'api-key':'XXXXXX', 'Content-Type':'application

问题 We need to create a field for an Index that is not going to be tokenised but still be searchable. In Azure Search if you make a field searchable, then the contents of the field are tokenised. If you make it filterable (documentation says then it wont be tokenised) then you cannot search it. In Lucene a KeywordAnalyzer does this job. Since Azure Search is also using Lucene cant understand why we cannot store a field contents AS IS in the index for searching WITHOUT splitting all the words

问题 We need to create a field for an Index that is not going to be tokenised but still be searchable. In Azure Search if you make a field searchable, then the contents of the field are tokenised. If you make it filterable (documentation says then it wont be tokenised) then you cannot search it. In Lucene a KeywordAnalyzer does this job. Since Azure Search is also using Lucene cant understand why we cannot store a field contents AS IS in the index for searching WITHOUT splitting all the words