azure-cognitive-search

问题 When defining a custom analyzer for Azure Search there is an option of defining a token filter from this list. I am trying to support search of both prefix and infix. For example: if a field contains the name: 123 456, I want the searchable terms to contain: 1 12 123 23 3 4 45 456 56 6 When using the EdgeNGramTokenFilterV2 which seems to do the trick, there is an option of defining a "side" property, but only "front" and "back" are supported, not both. the "front" (default) value generates

问题 My azure search indexer which reads from an sql table with Change Tracking, is failing with the following error "Unable to cast object of type 'Newtonsoft.Json.Linq.JObject' to type 'System.String'." If I reset the indexer, it'll start working fine. What is the root cause of the problem here? 回答1: We’ve identified an issue in SQL indexers that use SQL integrated change detection that affects a very small number of customers. We’re working on a fix, which will probably be deployed in

问题 I was playing around with the select for querying the index. I wanted to return a distance for a GeographyPoint I have in the index. I was trying something like this: where GeoPoint is the location field $select=ID,geo.distance(GeoPoint, geography'POINT(-122.131577 47.678581)') Is there a way to return distance in a Select statement if you have the lat and long and the location? Thanks! 回答1: Azure Search does not currently support returning the result of geo.distance in the search response.

问题 We have a azure web application where in there is one search box, when we enter text with double quotes like "App Service" it list records with "App service" however it also includes records having special characters in between the words like "App/Service". We want the search engine to return records that match the search phrase exactly (don't include records having special characters in between the search terms). 回答1: In this scenario, you want to index the entire content of a field as a

问题 I have a database comprising of the following schema depicting the linkage between individuals who connect with multiple Advisors and these Advisors have affiliations with multiple organizations Individuals--> Advisors (m:n relationship) Advisors --> Enterprises (m:n relationship) The business need is to enable search on all these concepts and organize results around AdvisorIds. As an example, display of a search result could be as follows a) Advisor1-> connected to Individuals A,B,C; and

问题 The last few weeks we have been experiencing this error message while using the Azure Search SDK (1.1.1 - 1.1.2) and performing searches. We consume the Search SDK from internal APIs (deployed as Azure Web Apps) that scale up-down based on traffic (so there could be more than 1 instance of the APIs doing the searches). Our API queries 5 different indexes and maintains an in-memory copy of the SearchIndexClient object that corresponds to each index, a very simple implementation would look like

问题 I am very new to azure search, basically i have created database and one collection this collection have few documents, also i have created one index . I am using REST API to search documents, 1) my rest api service is given below . GET https://xxxx.search.windows.net/indexes/[xxx]/docs?search=xxx&searchFields=xxxx&api-version=2015-02-28 2) My document is :{ "abc":"abcvalue", "xyz": { "key":"value", "kay1":"value1" } } Search result out put is : { "@odata.context": "https://xxx.search.windows

问题 1) Suppose I use the Azure Search API to upload a new document: POST /indexes/[index name]/docs/index?api-version=[api-version] 2) I get a response with an HTTP code 201 (document was successfully created) 3) I use the API again to DELETE to newly uploaded document Can I be 100% sure that the document will be eventually deleted? Or will it fail if the indexing process has not complete? 回答1: I work on the Azure Search team. Once you get a success code (HTTP 201) from the indexing API it

问题 I have an index in azure search which has the following json "id": "1847234520751", "orderNo": "1847234520751", "orderType": "ONLINE", "orderState": "OPROCESSING", "orderDate": "2018-10-02T18:28:07Z", "lastModified": "2018-11-01T19:13:46Z", "docType": "SALES_ORDER", "paymentType": "PREPAID", "buyerInfo_primaryContact_name_firstName": "", "buyerInfo_primaryContact_name_lastName": "", "buyerInfo_primaryContact_email_emailAddress": "test@gmail.com" I have indexed almost 0.8 million documents and

问题 1) Suppose I use the Azure Search API to upload a new document: POST /indexes/[index name]/docs/index?api-version=[api-version] 2) I get a response with an HTTP code 201 (document was successfully created) 3) I use the API again to search the newly uploaded document Can I be 100% sure that I will get the document in the results? Or could there be a delay in the indexing process? 回答1: No, it's not guaranteed the document will be returned in the query. The usual delay is on the order of seconds