It's helpful for the client to know the total number of results that match a query, so e.g.,
- it could be reported to the user as feedback and if it's too large, the user could then enter more constraints to narrow the search, etc.
It seems Azure Search doesn't currently work with append blobs. We use append blobs for logging and Azure search would help a lot if it could handle the blobs.1 vote
Belatedly marking as completed – this has been available for a long time.
How long did the query run for? (Plus any other appropriate measurements). This would help benchmarking, testing and maintenance of a search service by helping to identify the slowest queries.1 vote
Hi Harold, we do return elapsed time for a query in an HTTP response header. Originally this wasn’t documented, but we updated the docs. There’re probably many other measurements and analytics we could provide – if you have specific ideas, please submit there!
I can't delete an index as it is stuck in creating state. Please provide controls to force deletion of indexes which are stuck in creation state.1 vote
The index was stuck in Creating state due to a bug on our side – eventually we identified this “partially created” index and removed it, so you should be able to recreate this index now. Please let me know if you’re still having issues.
I apologize for the inconvenience this has caused for you.
Thank you for using Azure Search.
I am now stuck at recreating indexes. I was told to delete one of my index to create another, but it didn't work. The funny thing is that, I am only having just 1 active index in that Azure Search Repo.
Response that i get when I want to 'Import Data':
'You have exceeded the free quota of 3 indexers. Please delete one to continue'1 vote
Hi, the error message refers to indexers, not indexes. An indexer is a resource separate from an index. So in your case, you need to delete some indexeRs.
Also, please use MSDN forums or StackOverflow (azure-search tag) to ask questions like this – you’ll get a much faster response on those forums.
Azure Search team
Extend the Azure Search indexer for Azure tables to allow a search index to be sourced from multiple tables
Would it be possible to extend the Azure Search indexer for Azure tables to allow a search index to be sourced from multiple tables? I have a search that, currently, I build from a ProductAnnotation and a ProductWholesale table (both share a common Id for lookup and this Id is stored in the search index).1 vote
This is already possible in a slightly different form: you can create multiple datasource / indexer pairs all writing into the same index. As long as you stagger their schedules so that the indexers are unlikely to overlap on the same document at the same time, you’ll get the functionality this suggestion asks for.
Hope this helps!
Your Azure Search team
When indexing CSV blobs with Azure Search blob indexer, please add support for delimiters other than ",". We have many blobs that use | and \t as delimiters.1 vote
This functionality is now available. Please see https://docs.microsoft.com/azure/search/search-howto-index-csv-blobs#setting-up-csv-indexing
Thanks for using Azure Search!
Have a good weekend,
Your Azure Search team
Similar to what Azure Table is doing. Replace and Merge can be two different operations.
With the current implementation in the SDK, because C# object types are not dynamic, to merge, we will either have to get the object first, do a manual merge (basically a replace), or use a dictionary object contains only property-value pairs we need to update.
I think Azure Table's separation of Replace and Merge is easier to use. So when I call Merge with a model object, I don't have to worry about some fields get deleted because their value is null.1 vote
We’ve added test coverage to the .NET SDK to ensure that the merge scenario works as expected.
Indexers convert uniqueidentifier to lower case which should not happen.1 vote
Please look custom analyzers (https://docs.microsoft.com/en-us/rest/api/searchservice/custom-analyzers-in-azure-search), specifically a Token Filter to help convert to lowercase.
Require API for managing star/popularity/reputation ratings0 votes
Allowing control of date ranges during searches0 votes
When I test the service for JSONP support (by adding a &callback=myFunction argument to the querystring in Fiddler), the API is not returning a function. Because of this we are not able to call the cross domain service.
[User 2] CORS is better for our specific use cases though it is not supported for older browsers.0 votes
We need to be able to support the few hundred QPS requirement without slowing down0 votes
When I post a document with columns that dont exist in the index schema, it currently rejects the document. We would like the ability to post documents to the index with columns that dont exist in the index. Of course, there is no expectation that these additional columns will be processed in any way (except perhaps returned when all columns are requested in the search query)0 votes
- Don't see your idea?