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
-
Return the request URL when running a query operation
It would be great if the query operation would return the original request's URL. Thus, it would be possible to parse the request back to the facets used on the query, which would help in having the correct selected facets shown on the search results page rather than have them saved in a middle repository (cookie, cache, posted etc.).
10 votes -
OpenSearch support for search federation
Many companies use SharePoint as their entry point for search but federate actual searching across other data stores/sources.
22 votes -
Make errors and warnings as helpful and constructive as possible
Please try not to provide cryptic error and warning statements that are only understandable by project developers but rather try to provide HELPFUL and CONSTRUCTIVE errors and warnings that more quickly help the poor user.
I'm a newbie who quickly encountered the error:
400: {"result":{"Message":"Missing request parameters: definition"}}
when I tried to create a new index without a fields element. Why couldn't it provide (it certainly "knows" what the problem is) a more helpful, constructive error like
400: {"result":{"Message":"Missing required fields element when creating a new index"}}
11 votesWe are taking this feedback and working to improve our messages.
-
Relate Documents using Multiple Columns
We are also looking for a way to relate documents using one or more columns if possible (for example, a master document is related to others with a stringList column of IDs), and when a match occurs in the master document metadata, the related documents (or their IDs) are also returned in the results. for example, one of our use cases is to search a text in a set of master documents, and then present results which also include documents that are related to the main document
4 votes -
Semantics/tag clouds/concepts
Semantics/tag clouds/concepts
6 votesThis feedback is overly broad. Please provide some examples of queries you’d like to be able to execute.
-
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 -
StorSimple
Search over file shares in StorSimple
3 votesWe are considering adding crawlers for common stores and will also be looking a best practices for other stores.
-
Support for M Query Language
This one might be out of left field but I'd love to see an Azure object that can be configured via the M language ie: if I want to design some screen scraping that is used as a source of data for searching, it'd be nice to be able to design it using Data Explorer, then be able to just script out the M language code and paste it in. This would allow adding search to a site that doesn't allow access directly to a database.
4 votes -
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/72Multipart.html) would be more meaningful.
2 votes
- Don't see your idea?