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
-
Auto Suggester field order
Hi Team,
We are using Azure search for 2 yaers now. We have a requirement where we want to show auto suggester in some order. Say if we have 3 fields as auto suggestor[Name, title, city]. We want that the value from Name should come first then the remaining ones1 vote -
Add search/filter text box to left CMDLETS, RUNBOOKS, & ASSETS panel
Add search/filter text box to left CMDLETS, RUNBOOKS, & ASSETS panel to ease in selecting various items. Currently the full list of CMDLETS is very long to find the one you want.
1 vote -
Azure Blob Storage soft delete is not compatible with Azure Search
To track deletions, a soft delete policy is required in the data source. Something Azure Storage supports. However, it is not compatible with Azure Search. This should be an out-of-the-box feature in Azure Search.
1 vote -
Remove basic plan field count limits
Why is there field count limits? Lucene itself doesn't impose field count limits. 100 on the basic plan is very small especially considering that once you use blob storage indexing it consume about 10% of your field counts.
I've developed a product to have Umbraco CMS based indexes hosted in Azure Search but it's problematic due to the field count limits since 100 is very easily reached. Even 1000 doesn't seem to need to exist. Things like Elastic and Solr have this configurable and not a hard limit.
1 vote -
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 -
The pricing and option for app services, not corresponding wiht the real options
Update princing options.
1 vote -
Allow limiting blob documents to be indexed based on a specific metadata value
We only want to index a subset of documents in our blob container and in order to do so now, we have to have two blob containers and manage them. Similar to how you can limit document types to be indexed or not, the ability to restrict the scope of Blob objects based on a metadata value would help reduce our operating expenses and document management overhead. We could add a new Metadata name called "AzureSearch" and if set to "true", would be picked up by the indexer. Removing it from the index would simply require changing that value and…
1 voteThank you for the feedback. Please let us know if this article helps your scenario: https://docs.microsoft.com/en-us/azure/search/search-howto-indexing-azure-blob-storage#using-blob-metadata-to-control-how-blobs-are-indexed
You can specify if a blob should be skipped during indexing by modifying that blob’s metadata.
Thanks,
Mark
Azure Search Product Team -
TLS configurable property
Could we have a configurable property to set the minimum TLS version that search service will accept (as per Redis Cache and other resource types). With the removal of 1.0 and 1.1 on 6th Feb 2020 it would have been useful to set in advance to ensure that all endpoints talking to it were using 1.2 - I would assume that this same scenario will exist in the future when new versions make 1.2+ obsolete.
1 vote -
Annoying ListAdminKeys in Activity Logs
It seems that Azure Search has not Activity Logs blade. But when I see the whole Activity Logs of a subscription, there are so many ListAdminKeys activities of Azure Search resource.
1 voteThank 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 -
الفئه
ختراق فيس بوك
1 vote -
Pause play functionality
Functionality to start and stop the azure search service
1 vote -
Japanese OCR character split problem
OCR Cognitive Skill is described in Docs as being compatible with ja (Japanese), but when actually used, Japanese words are output with each character separated by a space, so the index is properly Cannot be created. This is a fatal problem.
Now I'm creating a custom skill to add the process of removing the read space, but it's not perfect.
1 vote -
Sub aggregation or pivot
Can we get solr pivot or sub aggregation equivalent functionality.
1 vote -
add server cpu usage metric for azure search machines
I would like to get metrics for our azure search machines cpu in order to get a clear picture of put resources usage
1 voteWe have no plans to surface the CPU, or other resource consumption, of the infrastructure that powers Azure Search. We’re looking to go in a direction where you don’t need to think about the underlying machines and only need to be aware of the search API and data in your search service.
Thanks,
Mike Carter
Azure Cognitive Search -
No way to offset when sending pages to Azure Search
When using Azure Search entity recognition with larger documents, there is no easier way to mark an offset for each page based on the position in the text. This makes it difficult to join the entities returned afterwards.
1 vote -
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 -
Review of Knowledge Store
I wrote a technical review of the Knowledge Store preview feature and wanted to share it with you. See attached.
1 vote -
Re-Indexing framework
Azure Cognitive Search should allow for ease of rebuilding index from scratch without impacting the existing search. Flexibility in custom ingestion should also be allowed.
1 vote -
Allow changing of attributes of a field once data has already been indexed
Common attributes users want to change are type (like int to string), doc-values, stored, indexed etc.
1 vote -
Improve SLA to 99.99%
The current SLA is only 99.9%. That is out of sync with typical enterprise SLAs of 99.99% that our own applications must abide to for our customers.
Hence, this lower than typical SLA endangers our own SLAs. Please improve to 99.99%
1 vote
- Don't see your idea?