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
-
Export/Import search indexes
Allow users to export and import search indexes. Creating a search index via the portal takes quite a bit of time and if the service has to be moved you end up doing it all over again.
250 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Vinod
Azure Search Product Team -
Backup/Snapshot of Index
It should be possible for us to snapshot our indices at an interval of our choosing. The location for the snapshot should be Blob Storage.
Why
A data load goes wrong. Currently you are stuffed if this happens. You have no way to rollback.
You want to take a production index + data and restore it into UAT/TEST/DEV. Currently there is no way to do this other than to load from source.
239 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Elad
Azure Search Product Team -
Indexer for Azure File shares
Index Azure File shares similar to blobs
222 votesPrivate preview of this feature is now available.
If you’re interested in participating, please email azuresearch_contact@microsoft.comThanks,
Azure Search team -
Possibility to delete documents that correspond to a filter
It would be useful to be able to remove from an index documents that correspond a specified filter or a facet. Currently you need to retrieve all those documents from the index and only then can you delete them.
218 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Luis Cabrera
Azure Search Product Team -
Time to Live for data
Also nice to have feature would be to purge data which is more than x days old by issuing explicit command or having TTL on documents.
209 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Mike
Azure Search Product Team -
Allow handling spelling errors in search "Did you mean ''?"
It would be really nice to have spell check and auto correct as part of search.
207 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Luis Cabrera
Azure Search Product Team -
Add support for field collapsing
I've utilized field collapsing (aka result grouping) quite a bit utilizing Solr. Being able to group results together by a common element, then being able to page and sort based on that result list.
176 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Liam
Azure Search Product Team -
Provide method for escaping characters in the search string like UrlEscape
Special characters must be escaped to be used as part of the search text. You can escape them by prefixing them with backslash (). Special characters that need to be escaped include the following:
+ - && || ! ( ) { } [ ] ^ " ~ * ? : \ /
Is there a built in method, basically the equivalent of UrlEscape, which can do this, or is every developer actually expected to do their own implementation?172 votesThank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
Thanks,
Mike
Azure Search Product Team -
Support geo.distance in select result
Azure Search does not support returning the distance data from geo.distance in search results. geo.distance can be used in only filter and orderby.
I would like to get distance data from geo.distance.
170 votesThank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
There are a few ways you can do this currently in code per document, for example (https://stackoverflow.com/questions/6544286/calculate-distance-of-two-geo-points-in-km-c-sharp). But we are considering how we might make it available as a document property.
Thanks,
Vinod
Azure Search Product Team -
Allow create, update, delete of Data Sources, Indexes, and Indexers with Service through ARM templates
You currently can only create a service instance through an ARM template, you then need to make REST calls to create, update, or delete Data Sources, Indexes, and Indexers. This makes using Azure Search a challenge in solutions that are released in a Continuous Delivery model. If I want to use Release Management in VSTS to automate deployments, I need to write additional PowerShell scripts to call Azure Cmdlets to get the Primary Key for the service, then call REST APIs through PowerShell, and suck in JSON files to send as part of the request. It's a very complicated process…
161 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Luis Cabrera
Azure Search Product Team -
Azure Search Alerts
Azure Search should have alerts similar to Azure SQL database. For example, I should be able to set up an alert to warn me if my index is almost full, et.c
159 votes -
Add support to search Sharepoint Document Library directly
Customer has a lot of documents in SharePoint document library that they want to be able to Search.
158 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Luis Cabrera
Azure Search Product Team -
Storage Optimized tier in the Basic tier pricing range (L0)
For a small business with low traffic and data just over the 2GB limit of the Basic tier it´s really hard to justify to upgrade to standard tier for 3.3x more cost. The performance and scaling for Basic tier is more the enough but the 2GB limit is just to low.
It would be nice if you could introduce storage optimized layer(L0) for the lower end of the price range where performance and scaling is not important but the storage amount is more than 2GB.154 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Mike Carter
Azure Search Product Team -
Support Explain API
The explain api computes a score explanation for a query and a specific document. This can give useful feedback whether a document matches or didn’t match a specific query.
154 votesThank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
Thanks,
Vinod
Azure Search Product Team -
Support for disaster recovery/failover
This would ensure high availability in case a DC goes offline/down so that customer doesn't need to write data to multiple geo-located accounts
151 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Elad
Azure Search Product Team -
Index specific admin keys
As of today Azure Search providee index specific query keys, but only global admin keys. In a multitenant scenario all tenants then have to share the admin key in order to index data. In order to provide sufficient tenant isolation in multi-tenant scenarios we need index specific admin keys. Especially for those cases where each tenant run in process isolation - hence the individual tenants can't access other tenants connection strings.
146 votesThank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
Thanks,
Vinod
Azure Search Product Team -
Support correlated search on complex collections
Now that Azure Search supports complex types, it would be useful to be able to combine full-text search and strict Boolean filters when querying over complex collections. Currently this is not possible -- search.ismatch()/ismatchscoring() are not allowed in lambda expressions, and using sub-fields of complex collections in full Lucene queries has uncorrelated semantics.
For example, if you want to search for hotels that have deluxe rooms with city views, none of these gives you exactly what you want:
search=Rooms/Description:(city views) AND Rooms/Type:(Deluxe Room)
search=Rooms/Description:(city views)&$filter=Rooms/any(room: room/Type eq 'Deluxe Room')
$filter=search.ismatchscoring('city views') and Rooms/any(room: room/Type eq 'Deluxe Room')
Instead, what you'd…
136 votes -
Support custom dictionary
Some domestic senario like, Legal, really domestic topic require custome dictionary for more accurate wordbreaking, stemming and normalization. I think custome dictionary with easy maintemance like SharePoint or FAST provide today is help this type of senario.
129 votesThis item has been marked as Started by mistake. We don’t have a short-term plan to deliver this feature but it is on our roadmap.
-
Support Azure Active Directory Password Authentication in Azure Search SQL indexer
Currently, using AAD Password Authentication mode as described in https://docs.microsoft.com/en-us/azure/sql-database/sql-database-aad-authentication-configure#active-directory-password-authentication-1 fails. Please support this option.
129 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Elad
Azure Search Product Team -
Document version support for data consistency and indexers
External Versioning Support
Are there any plans to support external versioning like the following: https://www.elastic.co/blog/elasticsearch-versioning-support
We are trying to migrate off of an Elasticsearch system where versioning support is being used to allow multiple Indexers potentially processing the same document (potentially different versions of the same document).
By using primary store’s version, we ensure that latest version of document is not overwritten by the older version of document.I was reading up on stackoverflow (http://stackoverflow.com/questions/28917204/azure-search-data-consistency) even with Etags support, it seems that each writer will need to read the document from AzureSearch to ensure it has the latest…
120 votesThank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
Thanks,
Liam
Azure Search Product Team
- Don't see your idea?