Azure Search
Azure Search is a search-as-a-service solution that allows developers to incorporate a sophisticated search experience into web and mobile applications without having to worry about the complexities of full-text search and without having to deploy, maintain or manage any infrastructure
-
Ability to specify a skillset to be used when adding documents to Search Index via DocumentsOperations SDK and REST API
Need to be able to specify the skillset to be used when adding documents to Azure Search index using the SDK (or even the REST API one - https://docs.microsoft.com/en-us/rest/api/searchservice/addupdate-or-delete-documents). Currently it's only possible by having an indexer. Please refer StackOverflow question for the scenario in which this would be useful:
https://stackoverflow.com/questions/54529101/using-a-skillset-when-adding-documents-to-azure-search-index/54539852?noredirect=1#comment95962064_545398523 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Luis Cabrera
Azure Search Product Team -
3 votes
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Liam
Azure Search Product Team -
Data security based on Gremlin graph API
Currently security data filtering seems just to be possible based on e.g. a group attribute and checking users group membership using oData filter expressions. When using CosmosDB Gremlin APIs the data is organized as vertices and edges, therefore the security filtering of search results should also be made possible based on Gremlin / subgraph expressions, not only based on oData filter expressions, ideally a possible combination of both. As an example consider a Graph: story (vertex) - belongs to (edge) - group (vertex) - has (edge) - members (vertices) ...and users should only find stories of THEIR groups (which they…
3 votesThanks for feedback. We’ll consider this for a future release of Azure Search. Feedback items are selected based on the number of votes they receive.
-
Translation missing on Azure Search portal
On the index field management page (Search Service > Index > Field) on Azure portal, we see some miss translation "検索可能" attribute in Japanese from "SORTABLE" attribute. It's too difficult to understand because the fields also have "SEARCHABLE" attribute which translated to "検索可能" attribute.
See the enclosed parts on the attached screen shots both Japanese and English.
My understanding is we should translate "SORTABLE" attribute as "ソート可能" one in Japanese.2 votesHi Shogo, we’re taking a look at this issue, Thanks for reporting it!
Eugene Shvets
Azure Search -
For the batch requests, leverage multipart content-type
For the batch requests (Index Population APIs), leveraging the multipart content-type (http://www.w3.org/Protocols/rfc1341/7_2_Multipart.html) would be more meaningful.
2 votes -
Create mechanism to increase the maximum running time for cognitive search skillsets or blob indexing with image analysis beyond 1 hour.
The limit of 1 hour is not enough for using the indexer with cognitive services using OCR.
1 voteWhile the OCR should not take that long, I think what you are saying is that indexers that require a bit of processing don’t index too many documents in a given time period (1 hour).
We are looking for mechanisms to improve throughput in our enrichment pipeline at this time. Thanks for the feedback!
-Luis Cabrera
Azure Search Product Team -
Drill down into queries
When looking at queries, while I'm interested in full queries such as "purple shoes" and "red blazers", I'd also like to see an index of the individual words that are used in the search terms, plus the ability to drill into the query list ie: which queries contained the word "blazer"? It doesn't have to be in the UI, as long as it's downloadable. (Ideally, it would be downloadable using REST-based queries and/or OData, and be consumable by Excel/Data Explorer in Excel/PowerPivot/Tabular data models in SSAS).
0 votes
- Don't see your idea?