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
-
Provide the ability to hibernate/revive the index
There are many scenarios where indexes are only needed for particular periods. A simple example is for demo purposes. I want to be able to have an index ready to use, but only use it periodically. It's too expensive to keep it running. It would be more 'cloudy' to have the ability to save/hibernate it to storage, and to be able to revive it from there. (I saw another suggestion to backup/snapshot. That's good but it also needs the ability to be deleted and still be recovered).
35 votes -
34 votes
We are actively evaluating this feature.
-
Random Scoring
See here https://www.elastic.co/guide/en/elasticsearch/guide/current/random-scoring.html
This has come up in the past on SO by other users as well.34 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. The workaround mentioned here is very cool, by the way!
Thanks,
Mike
Azure Search Product Team -
Please provide support for MySQL database for pushing data to the index from azure portal
Please provide support for MySQL database for pushing data to the index from azure portal
33 votesThis feature is currently in private preview (REST API support only, not portal support yet). For onboarding instructions, please email Victor Liu (victliu at the usual Microsoft domain)
-
Prospective search (aka percolator or reverse search)
It would be huge for my application to be able to do reverse searches a la Elasticsearch's percolator feature: Given a document ID, which saved queries would match that document.
32 votes -
Disable or replace TF-IDF for relevance computing
(Posting on behalf of Xu Lan)
To fit the needs of our search application, we would like to change the relevance computing by disabling or replacing TF-IDF.
Elasticsearch provides a mechanism to ignore TF-IDF: https://www.elastic.co/guide/en/elasticsearch/guide/current/ignoring-tfidf.html#ignoring-tfidf.32 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,
Luis Cabrera
Azure Search Product Team -
Increase Blob Indexer file size limits
The "Blob indexer: maximum characters of content extracted from a blob" limit seems rather restrictive, 32K for free, 64K for standard and 4MB for everything else. Plus when this limit is reached all you see in the azure portal is
[{ "key": null, "message": "Truncated extracted text to 32768 characters." }]
It'd be useful to know which documents are affected.
31 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Luis Cabrera
Azure Search Product Team -
Provide option to return total facet counts without all facet values included in response
We have facets with thousands of unique values, sometimes up to around 100k. In our UI, we'd like to show the top 10 or so values of each facet to allow the user to filter by them, but we have no need to display all 100k. That said, we need to display the facet *counts* so they know roughly how much data is being searched.
To do that currently, we have to set the facet counts arbitrarily high to make sure the accurate counts are retrieved, but that means we're getting back huge HTTP responses when really we just want…
30 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 an API for Text extraction from a file (or string/stream with file content)
Indexer https://azure.microsoft.com/en-us/documentation/articles/search-howto-indexing-azure-blob-storage/ does extraction of text from a file (document).
Instead of using azure blob (extra implementation and usage charge) and delay with processing a document from there, client will have possibility to extract text from document and do mergeOrUpload content.We know when file content was changed (or a new file created) and would like to handle that our self.
30 votesThank you for your feedback. We’re considering this for a future release of Azure Search. Essentially we need a push-API before document cracking and enrichment occurs.
Thanks,
Luis Cabrera
Azure Search Product Team -
Indexer execution status to App insights
Scenario: Thanks to the power of Azure, I have setup a indexer which continuously updates my index from the Azure sql db. Now I want to know if there are any errors while processing any document and why it failed to update the index(error message). This information is very critical for new documents or any document which is modified in the prod database. Note: Different teams do not have access to the Azure search service portal.
Current state: We already have indexer execution status but this information needs to be processed by another process by polling.
Ask: If this information…
29 votesI wonder if this article meets your needs:
https://docs.microsoft.com/en-us/azure/search/search-monitor-usageYou can send operation logs to log analytics to allow you to undestrand the health of your service.
Thanks!
Luis Cabrera
Azure Search Product Team -
MicrosoftLanguageStemmingTokenizer cannot process word 'F#' correctly
'F#' is a well-known programming language, but if you tokenize sentence contains 'F#' with "en.microsoft" analyzer, it will be omitted. However, 'C#' works fine and does not have such issue.
28 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Mike Carter
Azure Search Product Team -
Provide ability of collection Type field to be searched against individual values separately
For a document, where there are multiple values in its collection type column, it gives it lesser score (and hence either to come lower or may not even come in the result) to it even though the search query has matched with ONE of the values in the list COMPLETELY.
This is because, currently Azure Search considers list of all the values provided in the collection type as a single string by concatenating all of them.
My requirement is that if the search query (for that field) matches with any of the values in the collection, it should consider it…27 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 -
27 votes
The feature is available as a preview in our latest preview API.
For more details, please look for ‘moreLikeThis’ search parameter on https://azure.microsoft.com/en-us/documentation/articles/search-api-2015-02-28-preview/
-
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-documents26 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 -
Improve Faceting accuracy by having an option to count all records
For fields that have a large distinct value diversity, the faceting feature gives inaccurate results unless the count parameter is set to a number greater than the number of distinct values in a field. There should be an option in an index field that indicates to the search engine to count and facet all the values in a column. I realize this would hurt performance so it should be optional. But sometimes accuracy is more important than raw performance for consumers of your service.
26 votes -
Ignore thumbnails when indexing word documents
Word supports saving documents with a thumbnail which contains the text content from the first page. When Azure Search indexes documents, it also indexes their embedded documents. Generally speaking this is useful behaviour, but in this case it leads to content duplication of the first page.
We cannot control documents provided by users so Azure Search should handle this and ignore thumbnails when indexing Word Documents.
26 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,
Luis Cabrera
Azure Search Product Team -
Indexer (crawler) for Apache Cassandra API in Azure Cosmos DB
Add an indexer/crawler for Apache Cassandra API in Azure Cosmos DB
26 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Elad
Azure Search Product Team -
sintax highlight length
Could we get a parameter to specify the length of a highlight fragment that is returned when the highlight parameter is used on a field? The string returned is too short for some of our users because they are searching very techincal data and need more context. It would be very useful to be able to return longer fragments depending on the field we're searching so we need control over this.
25 votes -
Enable indexing of gzip compressed blobs
https://stackoverflow.com/questions/46245505/indexing-gzipped-blobs-in-azure-search
I am trying to setup Azure Search over Azure Blob. The json blobs are compressed using gzip.
When I try to index the blobs as-is, I get the exception :
"Error detecting index schema from data source: "Error processing blob https://mystorageaccount.blob.core.windows.net/mycontainer/urlencodedname with content type ''. Status:UnsupportedMediaType, error:""
Looks like Azure Search blob indexer does support indexing ZIP archives (application/zip MIME type), but not gzip-compressed files.
25 votes -
Elastic Azure Search
Provide an elasticity option as with Azure SQL Databases, for search it's a MUST HAVE feature!!!
25 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,
Luis Cabrera
Azure Search Product Team
- Don't see your idea?