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. Improve Faceting accuracy by having an option to count all records

    For fields that have a large distinct value diversity, the faceting feature gives inaccurate results unless the count parameter is set to a number greater than the number of distinct values in a field. There should be an option in an index field that indicates to the search engine to count and facet all the values in a column. I realize this would hurt performance so it should be optional. But sometimes accuracy is more important than raw performance for consumers of your service.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  2. Ignore thumbnails when indexing word documents

    Word supports saving documents with a thumbnail which contains the text content from the first page. When Azure Search indexes documents, it also indexes their embedded documents. Generally speaking this is useful behaviour, but in this case it leads to content duplication of the first page.

    We cannot control documents provided by users so Azure Search should handle this and ignore thumbnails when indexing Word Documents.

    26 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 →
  3. Indexer (crawler) for Apache Cassandra API in Azure Cosmos DB

    Add an indexer/crawler for Apache Cassandra API in Azure Cosmos DB

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  4. allow indexers to call DocumentDB stored procedures

    We have difficulty in transferring documents where we require multiple maps of our data into the flat search index. There is a limit of two user defined functions (which we use to do this) and there doesn't appear to be a way to call a stored procedure through the query language. Having the search indexers support DocumentDB stored procedures gives us far more power and flexibility to map the data correctly. At the moment we have had to revert back to writing our own code to do this.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  5. sintax highlight length

    Could we get a parameter to specify the length of a highlight fragment that is returned when the highlight parameter is used on a field? The string returned is too short for some of our users because they are searching very techincal data and need more context. It would be very useful to be able to return longer fragments depending on the field we're searching so we need control over this.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support for Postgresql for using indexers

    Please provide support for ingesting data from PostgreSQL, similar to the existing support for Azure SQL Database.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  7. 22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Scoring  ·  Flag idea as inappropriate…  ·  Admin →
  8. OpenSearch support for search federation

    Many companies use SharePoint as their entry point for search but federate actual searching across other data stores/sources.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Enterprise  ·  Flag idea as inappropriate…  ·  Admin →
  9. Language analyzer - ability to disable word decompounding

    Azure Search has word decompounding (in languages like German, Danish, Dutch, Swedish, Norwegian, Estonian, Finish, Hungarian, Slovak)
    https://docs.microsoft.com/en-us/rest/api/searchservice/language-support

    However often it doesn't lead to desired output as we need to find only compound words.
    Especially interested to have it in "et.microsoft" analyzer.

    21 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 →
  10. Change hit higlighting to handle line breaks as well as sentences

    It looks like the highlighting feature returns the full sentence around the highlighted term. This makes sense and works when the content has full stops in it.

    We are indexing documents which have bullet points and lists which do not have a full stop. As a result Azure search returns a large amount of content around the highlighted term.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. clone index

    I'd like to implement 'versioning' indexes for each DocDB repository.
    In example, DocDB collections are crawler-2016 and crawler-2015, each of which will be indexed to index-2016 and index-2015 in Azure Search.

    In this operation, 'Clone Index' button could be helpful greatly as I have to create each index one by one. Actually I screen-captured previous index fields and tick-tick index checkboxes which created from DocDB import datasource.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support filter min score

    Elasticsearch support "min_score" to filter documents by scoring.
    https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-min-score.html

    Can you add this feature to allow us to deal with irrelevant results please ?

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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 →
  14. term boosting in synonym map

    Synonym maps now exist as a preview feature, but the values mapped are considered truly synonymous. It would be great if we could basically use the synonym map feature and input a map that contains static term boosting.

    For example:
    castle => fortress^2, fort^1.5, stronghold^1.75, fortification^2, keep^2.7, citadel^1.8

    rather than
    castle => fortress, fort, stronghold, fortification, keep, citadel

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add a description field to index for better manageability between indexes with similar names.

    We create a lot of indexes for experiments. Over time it becomes harder to remember the differences between indexes with similar names. We could add something to the index name to distinguish them. But it makes the name messy. It'd be better to have a description field in index to describe what the index is.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add support to Blob indexer for OpenOffice formats

    Enable searching of OpenOffice documents stored in Azure Blob storage by adding support for indexing OpenOffice formats such as .odt, .ott, .oth, .odm, .ods, .ots, .odp, .odg, and .otp.

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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 →
  18. 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/4_7_0/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 →
  19. 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 →
  20. Allow access to stored term frequencies for searchable fields

    Term frequencies are maintained for searchable fields in order to compute things like TF/IDF quickly. It should be possible to access those term frequencies for additional analysis.

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

    Given the current API surface area of Azure Search, how would you actually use these term frequencies? Said another way, what other capabilities would you require in the API in order for term frequencies to actually be useful?

    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 Carter
    Azure Search Product Team

  • Don't see your idea?

Feedback and Knowledge Base