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. Support schema changes with automated reindexing

    Azure Search should support safe schema changes, such as deletion of fields, or maybe even safe field type changes (e.g., int -> string, or string -> string collection)

    745 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support "swapping" indexes

    Let's say you want to make some changes to an index, like changing from tokenized to indexed or from Edm.String to Collection(Edm.String), ... or even re-index all the data with some additional information.

    It would be great if we could have a "production" and a "staging" slot in an index (similar to Cloud Services for example) where we can do whatever we need to do in the staging slot, and as soon as we're ready (all data has been indexed), we simply swap the staging slot to the production slot and from that point on the new index is used.

    591 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  11 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  3. Increase the number of fields per index

    Using certain platforms or applications require the usage of over 1000 fields per index. The limitation is on the low end for a platform like Sitecore - can this be increased?

    252 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  4. Possibility to delete documents that correspond to a filter

    It would be useful to be able to remove from an index documents that correspond a specified filter or a facet. Currently you need to retrieve all those documents from the index and only then can you delete them.

    187 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  5. Time to Live for data

    Also nice to have feature would be to purge data which is more than x days old by issuing explicit command or having TTL on documents.

    170 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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 →
  7. 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 →
  8. Extract text in a readable manner for pages using landscape orientation in PDF

    There is a known issue with PDFs that display certain pages with text oriented in a vertical manner. The issue is not that the text is not extracted, but rather that it is extracted in an unreadable manner since current extraction methods expect text to be horizontal. Unfortunately there is not currently a work around within Azure Search.

    We would need to inspect thousands of documents and rotate the vertical/landscape pages of the PDF manually before it can work as expected.

    59 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  9. 59 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  10. 52 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 →
  11. 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 →
  12. Extend spatial features to allow indexing and searching of polygons and multi-polygons

    Extend spatial features to allow indexing and searching of polygons and multi-polygons

    20 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 →
  13. Implement Data Lake Gen2 Search Indexer

    It seems like MSFT is pushing Data Lake as a more robust implementation of Azure Blob.

    Implementing a Data Lake Gen2 Search Indexer would give my team confidence that Azure Search will align with our move to Data Lake.

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  14. It would be very useful, for the sake of more accurate suggestions, to provide the equivalent of SolR ShingleFilterFactory. This would let u

    It would be very useful, in order to provide more accurate suggestions, to have the equivalent of SolR ShingleFilterFactory (http://lucene.apache.org/core/470/analyzers-common/org/apache/lucene/analysis/shingle/ShingleFilterFactory.html).
    This would let us give the user suggestions with actual groups of words found in the index.

    17 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 →
  15. Make the blob indexer faster

    From the tests I made, currently a single blob indexer in S2 with 1 partition and 1 replica is only able to process between 50 000 and 75 000 small office documents (1 to 4 pages) in a 24 hour period.

    The current solution which would be to restructure millions of blobs into "directories" with max 75 000 blobs in them and have 12 indexers is completely out of the question due to the insane pricing model and the time it would take to both, modify consumers with new paths and move blobs to a new structure. The latter being…

    17 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 →
  16. Support Decimal / Money Datatype

    Please add support for Decimal / Money datatype in index schema.

    16 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 →

    Thank you for your feedback. We need some more information before we can take action on this request.

    Can you share some more context re why you need a decimal (vs. the EDM.double that we support today) or money? Do your fields include signs like $?

    As a workaround, with the recent release of Cognitive Search, you can create a custom skill to transform any field

    Thanks,
    Elad
    Azure Search Product Team

  17. Managed service identity support

    Indexing Azure Storage requires a storage account key which makes it more cumbersome to rotate that storage account key. Indexing Azure SQL DB requires a username/password making it more cumbersome to rotate that password. Please allow us to enable a Managed Service Identity (MSI) for Azure Search so that we can index data sources using that identity rather than with account keys and passwords.

    14 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 →
  18. Support an Azure SQL Data Warehouse as a data source (with enable change tracking).

    It would be useful to be able to connect a SQL DW table to an index. I did try this but it seems SQL DW does not support the ENABLE CHANGE_TRACKING option so that means I could not synch changes which is key. Also I believe Azure search needs a PK on the table to manage changes - and DW does not use primary keys. So it may need new features in SQL DW first.....

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Indexing  ·  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.

    One thing we will also require for your request is for Azure SQL database to support Integrated Change Tracking as seen in SQL Server.

    Thanks,
    Liam
    Azure Search Product Team

  19. Add more document allowance to the free tier

    Thank you for the Free Tier!! We really love it! Just one thing to ask. Is it possible to add more document capacity to the free tier? We know you have to cut it off somewhere but 10,000 is just a bit small for eval purposes when working with big datasets. Maybe 100k or 150k?

    11 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 →
  20. Allow to rename search index column

    Allow to rename search index column

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

    Thank you for your feedback. This is a fair suggestion and something I’d agree we should support. We’re considering this for a future release of Azure Search. Suggestions are typically addressed based on the total number of votes received.

    Thanks,
    Mike Carter
    Azure Search Product Team

← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base