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
-
Offer Elastic Search as PaaS service
Offer Elastic Search as PaaS service or managed cluster like Redis.
Do not want Azure search but the native ES as service with its native interface and api.90 votesThank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we are actively exploring this for future releases. If you are interested in more information – please contact us at azuresearch_contact@microsoft.com.
Thanks,
Elad
Azure Search Product Team -
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.
90 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Elad
Azure Search Product Team -
Support 'skip' in facet queries
Currently the results of facet queries can be limited adding the "count:n" parameter to select only the top n results.
If one is interested in seeing all results of a facet query, there is no other way than setting the 'count' value sufficiently high to make sure that all result are included in the response.
In the scenario of a large number of distinct values for the facet field those queries may, however, result in a large response with poor performance.
In order to be able to provide paging through facet results for better performance, it's necessary to have a…85 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 -
Add support for using Azure Data Lake with blob indexer or new indexer
Customer would want to use ADL as a centralized store and then use various services like Azure Search, HDInsight on top of the same document store
83 votesWe are happy to announce a public preview of an indexer that supports Azure Data Lake Storage Gen2 as a data source.
Request access to the preview here:
https://aka.ms/azure-cognitive-search/indexer-previewMore documentation on the preview indexer:
https://docs.microsoft.com/azure/search/search-howto-index-azure-data-lake-storageThanks,
Mark Heffernan
Azure Cognitive 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…
81 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 -
Implement other highlighters
Right now only Postings highlighter is implemented, which highlights single terms instead of full phrase query. Would be good to have other highlighters.
As said here : https://stackoverflow.com/questions/42411353/azure-search-highlights-for-phrases-with-double-quotes80 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Liam
Azure Search Product Team -
Support for Geo.distance function on customer location compared to index data
We have clients that we want to expose using the search feature. They do not want to appear if customer is outside there catchment area.
The Geo.Distance function can only be compared to fixed data.
I'd like to compare this with data held in the index.70 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 -
Provide option to facet on all facetable fields in a Search request
Some applications can have a large number of facets and it is inconvenient to have to specify them all explicitly in the Search API, as reported here: http://stackoverflow.com/questions/28542665/azure-search-what-if-i-have-a-lot-of-facets
If there were an option like facet=* that returned facets on all facetable fields, that would be easier for such cases.
69 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,
Elad
Azure Search Product Team -
Extend Tag Boosting by "searching" instead of "filtering"
Azure Search with Tag Boosting will give a boost to documents that have "exact" tags in common with the input query.
If a tag in index is "salt lake city" and one from query is "salt lake", the document doesn't get a boost. Even worse, since I believe Tag matching is using "filter" routine, it is case-sensitive.
Yes, we can do multi-column search, but one column search with tag boosting is a way more fast and returns better relevance results focusing on the main column.
So it would be great if Azure Search extends the current Tag Boosting to use…
60 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Mike
Azure Search Product Team -
Add machine learned ranking models
Similar to Solr's (small) capabilities
https://cwiki.apache.org/confluence/display/solr/Learning+To+Rank59 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Vinod
Azure Search Product Team -
Allow suggestions for custom analyzers
Just what the title says.
59 votesThank you for your feedback. You can include a field with a custom analyzer in suggest API. More information is needed before we can take action on this request.
Thanks,
Mike
Azure Search Product Team -
Extract text in a readable manner for pages using landscape orientation in PDF
There is a known issue with PDFs that display certain pages with text oriented in a vertical manner. The issue is not that the text is not extracted, but rather that it is extracted in an unreadable manner since current extraction methods expect text to be horizontal. Unfortunately there is not currently a work around within Azure Search.
We would need to inspect thousands of documents and rotate the vertical/landscape pages of the PDF manually before it can work as expected.
58 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 should be able to index Cosmos DB Table API accounts / collections
Similar to the suggestion for MongoDB support
56 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Liam
Azure Search Product Team -
55 votes
Thank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Liam
Azure Search Product Team -
Azure Search deployed within Virtual Network
I would like suggest Azure Search could be deployed in virtual network so that not expose the search service endpoint to internet.
53 votesWe have started working on this, however at this time we do not have a committed date that we can share.
-
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…
50 votes -
Provide sum and average on facet
It would be nice to have agregation on certain facetable Field.
We would define another numeric field to be computed.On the FacetResult, we could get sum and average exactly in the same way as count.
48 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 expressions in $orderby
Let us have an Azure Search index with three columns:
1. Id [Edm.String]
2. Tags [Collection(Edm.String)]
3. MaxScore [Edm.Int32]The index contains the following two entries:
Id Tags MaxScore
1 Paris,London,Rome 30
2 Paris 10We have also a scoring profile and a scoring function of type Tag (Sum, Linear) which evaluate every tag by 10 points (boost = 10).
We want to search the records with tags "Paris, London" in this index and sort it according to the percentage of compliance, while 100% is the value in column MaxScore.
The problem is that by default Azure Search sorts records…
47 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Liam
Azure Search Product Team -
Run multiple Indexers at once
We have many indexes with matching indexers that scan SQL Server tables to import/update data.
I found that during the initial import of a new large index (millions of records, taking several hours), none of the other indexers on the same service are run at all. This means that just by adding a new index, all other indexes will become stale until the large index is finished!
Please add the ability for multiple indexers to run simultaneously.
45 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 -
Adding hard delete policy to all of Indexer
Can we add hard delete policy to all of indexer as same as soft delete policy?
Some senario in custmer immideiately want to refect source change result. We know we can do it by making push base approach, but it's much easier and simplyer to ensure single data update way.Cosmos:
https://docs.microsoft.com/en-us/azure/search/search-howto-index-cosmosdb#indexing-deleted-documents45 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
- Don't see your idea?