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
-
Clone entire Azure Search instance, just like I can clone App Service.
I would be extremely handy if I could clone entire Azure Search instance to the same or a new Resource Group, in the same or a new location using the same or another Azure Subscription. Like I can clone Azure App Service wherever I want.
User case: If there is an issue which is reproducible with production instance of Azure Search, then I will clone in to a separate sandbox, and take it from there. As of today, I have to create a brand new Azure Search instance, clone SQL Database and reindex them to get the same data.
42 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 -
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.
42 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 -
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.
41 votes -
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-documents41 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 -
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
39 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)
-
Support picking existing index when creating an indexer in Azure Portal
Today is only possible to create an indexer if you follow the entire process through import data workflow:
-Select the data Source
-Add Cognitive skills (optional)
-Create an Index
-Create an IndexerHowever, there are times we want to set a different schedule for an indexer or create a new one, without recreating the index.
38 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 -
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.38 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 -
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…
36 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 -
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.35 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 -
34 votes
We are actively evaluating this feature.
-
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 -
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…
30 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 -
30 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/
-
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 -
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 -
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.
28 votes -
Elastic Azure Search
Provide an elasticity option as with Azure SQL Databases, for search it's a MUST HAVE feature!!!
28 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 -
Support scoring profiles on suggesters
I think it would be valuable to expand the capabilities of suggesters. Right now, they're somewhat limited. I think it would be nice if they provided the flexibility of scoring profiles. The reason why is because sometimes, it might be nice to show the most recently added or viewed documents (i.e. Edm.DateTimeOffset) as suggestions. Other times, you may want to show the most popular, or most viewed, documents (i.e Edm.Int32). These are just two scenarios that I would like to cover with suggestions, but, I'm a bit limited.
28 votesThank you for your feedback. This is an interesting suggestion, but it is unlikely we’ll address this in the near future. We’ll reassess based on the number of votes it receives.
Thanks,
Mike
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 -
Support IP firewall\service endpoints
Our enterprise requires 2 factor auth for all remote services. Please support IP based firewall and service endpoints!
27 votesThank you for your feedback. We’re considering this for a future release of Azure Search. Will supporting V-NETs for Azure Search be a good solution for your use case?
Thanks,
Elad
Azure Search Product Team
- Don't see your idea?