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
-
Modelling Complex Types in Indexes
When modelling an index the data types are restrictive. There are simple types and collections. There is nothing that allows us to model complex types e.g.
...
"name": {
"first": "Ericka",
"last": "Banks"
},......The oData spec allows for complex types
http://www.odata.org/documentation/odata-version-2-0/overview/
1,344 votesThis feature is now Generally Available: https://docs.microsoft.com/en-us/azure/search/search-howto-complex-data-types
-
Provide a startup-friendly billing model
For startups it might be interesting to split billing in 2: queries and storage (similar to the Windows Azure Storage billing model).
Our customer will have lots of records from day 1 (minimum 4 million), but the number of QPS will be very low the first weeks/months.So we might want to start with a shared instance in terms of QPS, but not for data / # documents.
713 votesI am happy to announce that this is now complete. We have released a new Basic Tier and you can learn more here: http://aka.ms/azuresearchbasic
Your Azure Search team
-
OCR for common image formats (GIF, JPEG, TIFF)
Extract text from image files.
355 votesThis functionality is now available to all customers as a part of Cognitive Search feature of Azure Search. See:
- Introduction to Cognitive Search: https://docs.microsoft.com/azure/search/cognitive-search-concept-intro
- Process and extract information from images: https://docs.microsoft.com/azure/search/cognitive-search-concept-image-scenariosPlease try it out and give us your feedback.
Thanks,
Your Azure Search team -
Blob Indexing w File Crackers
We would love to have blob containers indexed. One option may be to use iFilter support.
205 votes -
Azure Search and SQL Server integration
Integrating SQL Server (Azure and on-prem) with Azure Search. A search in table/column that is Azure Search enabled would fall into a Azure Search query in the background, not visual for the developer.
Only Azure Search enabled columns and tables would be handled by Azure Search and it would not be visible for the database consumer.
Only a Azure Search Package that is installed on a on-prem machine that would enable the DBA to define which tables or columns that should be Azure Search enabled. Database triggers for SELECT, INSERT, UPDATE and DELETE would translate into Azure Search REST based…
174 votesAzure Search now supports automatically indexing data in Azure SQL Databases and SQL Server in Azure VMs. For more details, see http://azure.microsoft.com/en-us/documentation/articles/search-howto-connecting-azure-sql-database-to-azure-search-using-indexers-2015-02-28/
-
Support startsWith, contains, and endsWith wildcard style queries
In simple query syntax wildcard style searches are supported. OData is great with its rich query support but is missing support for wildcard style searches like simple query syntax.
To me the easiest path for implementation would be to support the startsWith, contains, and endsWiths functions in OData.
178 votesPrefix, suffix, and infix searches are now supported through regular expression in the Lucene Query syntax. Please see https://azure.microsoft.com/en-us/blog/lucene-query-language-in-azure-search/ for details.
-
Allow customer to provide encryption key for indexed data
To meet enterprise security requirements, it would be great if index data could be encrypted (ideally with a key provided by the customer.)
140 votes -
Support for 2 Billion Documents
We have 2B very small records with relatively low QPS rate. The overhead with the crawl database alone is a massive challenge.
135 votesWe now have an S3 Azure Search tier that support over 1 billion documents. For more details, please see https://azure.microsoft.com/en-us/blog/new-azure-search-tiers-and-basic-and-standard-s2-general-availability/
-
add extra transactions
the 5,000 transactions are depleted in few hours, for a new website, that because of the crawling bots, i have 0 visitors on the website and all 5,000 transactions gone. The search api is useless!!!!
123 votes -
106 votes
Azure Storage now supports keeping blob data encrypted at rest. Please see https://docs.microsoft.com/azure/storage/storage-service-encryption. Azure Search seamlessly composes with storage accounts with encryption at rest enabled.
Thank you for using Azure Search, and please come the feedback coming!
Your Azure Search 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.
89 votesAzure Cognitive Search support for Private Endpoints is currently GA. More info: https://docs.microsoft.com/en-us/azure/search/service-create-private-endpoint
-
80 votes
This functionality is now available to all customers as a part of Cognitive Search feature of Azure Search. See:
- Introduction to Cognitive Search: https://docs.microsoft.com/azure/search/cognitive-search-concept-intro
- Predefined skills: https://docs.microsoft.com/azure/search/cognitive-search-predefined-skillsPlease try it out and give us your feedback.
Thanks!
Your Azure Search team -
HTTP POST based search query
I can see only HTTP GET is supported.
Hope I don't get a 414 (Request-URI Too Long) status if a URI is longer than the server can handle79 votesAzure Search now supports invoking Search and Suggest REST APIs via HTTP POST (previously you could only invoke them using GET). This is useful in scenarios where you have large filters and/or many facets and may be constrained by the 8 KB limit on the length of request URIs.
The new endpoints are now available in the 2015-02-28-Preview API version, documented here:
https://azure.microsoft.com/documentation/articles/search-api-2015-02-28-preview/#SearchDocs
https://azure.microsoft.com/documentation/articles/search-api-2015-02-28-preview/#Suggestions
-
Include search functionality
Incorporate Lucene/SOLR or microsoft search server into appfabric to allow searching across files (table/azure storage), databases, objects cached items, etc. Allow for cost effective cloud based storage + caching.
71 votesFull text search is now supported. Please visit: http://azure.microsoft.com/en-us/services/search/
-
DocumentDB indexer should be able to index MongoDb collections
If I create a MongoDB collection backed by DocumentDB, I should be able to use the DocumentDB indexer to ingest it into Azure Search.
69 votesWe are happy to announce that this feature is now available in public preview. For now, it’s only available using the Azure Search REST API.
Please see https://docs.microsoft.com/en-us/azure/search/search-howto-index-cosmosdb for details.Give it a try and let us know what you think.
Thank you for using Azure Search and for your continued feedback,
Your Azure Search team -
Support user-provided query in SQL indexer
Let's say I run an indexer to read a really large table, with a billion records, out of which I'm interested in only a few thousands. This is a database I do not own, and I have only read permissions to it.
In this case it would be better to have a simple filter on which data to keep in the indexer throw away the irrelevant data.
For eg: "Index this table where TeamName equals MyTeam"
Even though the indexer runs on a large set of data, my index would only contain a smaller subset of data.
Smaller the index,…
66 votesAd mentioned below, please create a View in SQL and then leverage this in the Indexer.
-
Analyzer with Automatic language detection
Our use case is that users upload files which can be in any languages, hence we have to do language identification on the content. Each file only exists in one language, meaning we don't have multiple translations of the same file.
For now that means we have to create one field per potential language in the index and assign them corresponding language analyzers. Then when we index the file we upload it's content to the field matching the language. Then when we add more field with the same language requirements we end up with spending a huge number of fields…
62 votesYou can accomplish this with a skillset and a custom language detection skill. The documentation for creating a skillset can be found here https://docs.microsoft.com/en-us/azure/search/cognitive-search-defining-skillset
Thanks,
Vinod
Azure Search Product Team -
Add OData syntax support for startswith, contains, and endswith queries
This is essentially a duplicate of another suggestion: https://feedback.azure.com/forums/263029-azure-search/suggestions/6470849
The original suggestion mentioned odata support, and while it was marked as complete, it was only added to lucene searches.
I'm sure many of the 178 votes where for specifically odata support.
58 votesPlease take a look at the search.ismatch filter function. It should give you the filter capabilities you are looking for by leveraging the Lucene search syntax in a filter without impacting the scoring of the results. More info: https://docs.microsoft.com/en-us/rest/api/searchservice/odata-expression-syntax-for-azure-search
Thanks,
Mike
Azure Search Product Team -
Cover Azure Search in the HIPAA BAA
Please add Azure Search to the HIPAA BAA so we can use it in healthcare software.
56 votesAs reported below, Azure Search is now HIPAA compliant. Marking this as complete.
-
Sort results by rank
We had also requested sort results by rank
54 votesYou can now use search.score() function in the ‘orderby’ expression to sort by relevance score explicitly. Details in our documentation: https://docs.microsoft.com/en-us/rest/api/searchservice/odata-expression-syntax-for-azure-search
- Don't see your idea?