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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Pricing based on transactional throughput, similar to SQL Azure

    The current model is a lot like the old SQL Azure models, where it was the volume of data that largely drove the cost of the service. SQL Azure became an affordable breakthrough when it shifted toward pricing based on overall transactional throughput (i.e., large databases that did not need to handle huge volumes were now affordable).

    Search should work the same way. If I operate a marginally popular web forum, for example, I may have several gigs of data to index, but the storage of that is the cheap part. It doesn't get a lot of queries, and new…

    295 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support for crawling HTML/websites

    Enable Azure Search to crawl a local HTML website

    274 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  3. 'Skip' limit should be far higher - int.MaxValue

    'Skip' is limited to 100,000 - which makes it impossible to iterate over an entire dataset, unless there's some meaningful way to segment the data set first.

    Given there's an upper limit on the complexity of the queries we can pass in 4500 chars (it seems?)

    It's very, very awkward to perform tasks on large complex datasets.

    233 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thank 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.

    There are major performance implications for supporting this which we will need to work through.

    Thanks,
    Vinod
    Azure Search Product Team

  4. Support geo.distance in select result

    Azure Search does not support returning the distance data from geo.distance in search results. geo.distance can be used in only filter and orderby.

    I would like to get distance data from geo.distance.

    138 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →

    Thank 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.

    There are a few ways you can do this currently in code per document, for example (https://stackoverflow.com/questions/6544286/calculate-distance-of-two-geo-points-in-km-c-sharp). But we are considering how we might make it available as a document property.

    Thanks,
    Vinod
    Azure Search Product Team

  5. Index specific admin keys

    As of today Azure Search providee index specific query keys, but only global admin keys. In a multitenant scenario all tenants then have to share the admin key in order to index data. In order to provide sufficient tenant isolation in multi-tenant scenarios we need index specific admin keys. Especially for those cases where each tenant run in process isolation - hence the individual tenants can't access other tenants connection strings.

    137 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Multi-tenancy  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support Explain API

    The explain api computes a score explanation for a query and a specific document. This can give useful feedback whether a document matches or didn’t match a specific query.

    122 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  7. Provide method for escaping characters in the search string like UrlEscape

    Special characters must be escaped to be used as part of the search text. You can escape them by prefixing them with backslash (). Special characters that need to be escaped include the following:
    + - && || ! ( ) { } [ ] ^ " ~ * ? : \ /
    Is there a built in method, basically the equivalent of UrlEscape, which can do this, or is every developer actually expected to do their own implementation?

    105 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  8. Pricing for more documents with less storage size / less documents with more storage

    It would be great to have a pricing model where we can index large amounts of small sized documents. (e.g.: 15M documents in 12 GB of storage).
    Same goes the other way around, less documents, with a greater storage size.

    102 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →

    The current Azure Search business model charges for storage consumed and not by document count. Thank 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

  9. Offer Elastic Search as PaaS service

    Offer Elastic Search as PaaS service or managed cluster like Redis.
    Do not want Azure search but the native ES as service with its native interface and api.

    90 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support 'skip' in facet queries

    Currently the results of facet queries can be limited adding the "count:n" parameter to select only the top n results.
    If one is interested in seeing all results of a facet query, there is no other way than setting the 'count' value sufficiently high to make sure that all result are included in the response.
    In the scenario of a large number of distinct values for the facet field those queries may, however, result in a large response with poor performance.
    In order to be able to provide paging through facet results for better performance, it's necessary to have a…

    85 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  11. Document version support for data consistency and indexers

    External Versioning Support

    Are there any plans to support external versioning like the following: https://www.elastic.co/blog/elasticsearch-versioning-support

    We are trying to migrate off of an Elasticsearch system where versioning support is being used to allow multiple Indexers potentially processing the same document (potentially different versions of the same document).
    By using primary store’s version, we ensure that latest version of document is not overwritten by the older version of document.

    I was reading up on stackoverflow (http://stackoverflow.com/questions/28917204/azure-search-data-consistency) even with Etags support, it seems that each writer will need to read the document from AzureSearch to ensure it has the latest…

    75 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support for Geo.distance function on customer location compared to index data

    We have clients that we want to expose using the search feature. They do not want to appear if customer is outside there catchment area.
    The Geo.Distance function can only be compared to fixed data.
    I'd like to compare this with data held in the index.

    70 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  13. Provide option to facet on all facetable fields in a Search request

    Some applications can have a large number of facets and it is inconvenient to have to specify them all explicitly in the Search API, as reported here: http://stackoverflow.com/questions/28542665/azure-search-what-if-i-have-a-lot-of-facets

    If there were an option like facet=* that returned facets on all facetable fields, that would be easier for such cases.

    66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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.

    45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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-documents

    Azure Table:
    https://docs.microsoft.com/en-us/azure/search/search-howto-indexing-azure-tables#incremental-indexing-and-deletion-detection

    44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  16. Run multiple Indexers at once

    We have many indexes with matching indexers that scan SQL Server tables to import/update data.

    I found that during the initial import of a new large index (millions of records, taking several hours), none of the other indexers on the same service are run at all. This means that just by adding a new index, all other indexes will become stale until the large index is finished!

    Please add the ability for multiple indexers to run simultaneously.

    42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Enterprise  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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 Indexer

    However, there are times we want to set a different schedule for an indexer or create a new one, without recreating the index.

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Scoring  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5
  • Don't see your idea?

Feedback and Knowledge Base