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
-
I wasn't able to apply fuzzy logic using search explorer
I should be able to apply fuzzy search using Azure cognitive service on my data source. Any misspells weren't yielding any results.
1 vote -
The pricing and option for app services, not corresponding wiht the real options
Update princing options.
1 vote -
Visibility/metric for the usage of MultiHoming for validating if it works as expected
We are looking to use the Multi-Homing feature for configuring the Azure search instance in the secondary region to retrieve data from the geo-replicated read-region instance of CosmosDB for making sure the dependencies are co-located in the same region. Though multi-homing feature is a great feature to resolve our multi-region requirements, there is no metric or visibility to validate if the setup is working as expected. We would like to have a metric to show which Cosmos DB instance the Azure search is indexing data from.
1 vote -
Offer reserved pricing on Azure Search (similar to AWS ElasticSearch)
AWS offers up to 52% discount when committing to a 3 year reserved instance for AWS ElasticSearch.
There is no reserved pricing option for Azure Search.
Please provide reserved pricing, similar to Cosmos DB/Azure SQL, at a discount comparable to AWS.
47 votes -
support indexing for Visio documents
Can we see support for indexing (or crawling) of Visio documents?
In the networking world, these are very important sources of data.
Visio documents are key information sources for design, intent and work planning when it comes to deploying and managing network appliances. It would be invaluable to engineers
4 votes -
Allow disabling of term frequency as a ranking factor
We built an internal order lookup tool. In many of these cases, proximity is absolutely valuable as a scoring factor, but term frequency has little to no value.
Right now, searching for "Jones Gary" will give higher ranking to an order that has the term Jones in both the customer name and in one of the address fields, putting it higher than a result containing Jones B Gary.
I've tied 'hacking' around it by adding a wildcard as described below, but it doesn't have the intended effect.
3 votes -
Pause play functionality
Functionality to start and stop the azure search service
1 vote -
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…
133 votes -
Please make it possible to rename an index.
Please make it possible to rename an index.
17 votes -
Azure Cognitive Search should increase the maximum limit of complex collection fields from 40 to something more appropriate for Json files.
I have json files having more than 70 complex collection fields. I want to index these Json files using Azure Cognitive Search, but unfortunately the limit for complex collection fields is only 40 for every tier.
I suppose the limit should be increased from 40 to something more appropriate.3 votes -
Support contains in azure search
In Azure search we need to support "contains".
example:
If I search for apple
then it show be give apple,apple fruit ,green apple ,green apple fruit.apple
6 votes -
higher numbers of scoring functions for higher pricing tiers
Azure Search should support higher numbers of scoring functions for higher pricing tiers, since they have more compute resources available.
Current limit is 8 function maximum regardless of pricing tier.
1 vote -
Hit highlight new behavior is not working
Accrording to doc Hit highlighting behavior updated on 15 July 2020,
but still I am getting same response as before,
I have recreate whole service on 16th July.Can not get exact match results in hit highlight
1 vote -
Azure Cognitive Search should be able to index Azure Files
Azure Cognitive Search should be able to index Azure Files. I have no way to search in Azure Files directly, if I store files in Azure Files instead of Blobs.
3 votes -
DataSource Definition JSON always shows Connectionstring = null (By Design)
DataSource Definition JSON always shows Connectionstring = null (By Design).
The recommendation is that, instead of null, says: "Hidden for security purposes".
1 vote -
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 -
Allow search management UI with Private Link enabled.
When the search service is configured with a private link or in private mode, we are unable to manage the Search Service outside of doing it programmatically or through the API. We would like an option to be able to manage the service when private link is enabled.
3 votes -
Sub aggregation or pivot
Can we get solr pivot or sub aggregation equivalent functionality.
1 vote -
Support contains/startswith/endswith in collection matching lambda expressions
It would be great if you support more operators in collection matching lambda expressions.
For example, Members/any(m: m contains 'a').
Since there's no correlation between the query and the filters, this can be very useful.4 votes -
Support additional file formats
Additional mail formats such as .PST, EDRM, Mbox
AutoCAD
DICOM3 votes
- Don't see your idea?