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 case-insensitive comparison in filters

    Searching with text=<xyz> performs a case-insensitive search. However, testing string fields in filters is case-sensitive. There should be a way to do a case-insensitive string comparison in filter expressions.

    713 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  16 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  2. Search multiple indexes at once

    The underlying elasticsearch technology supports making a single search query that searches and ranks results over multiple disparate indexes at once[1], but this functionality is not surfaced through the Azure Search APIs.

    Adding this would allow a single search to span over indexes with different schemas combined in a single correctly ordered result set.

    [1]: https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-index.html

    511 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  3. Case-insensitive sorting for string fields

    When querying the index, is it possible to do a case-insensitive $orderby on a string field? For example, we want to sort results by username but preserve the user's choice of casing. While we could workaround this by keeping a normalized version of the username alongside the original data, having this feature built-in would obviously be preferable.

    423 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  6 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support hierarchical facets

    Searching in a hierarchy is very common.
    E.g. Cars/Ford/Accessories

    409 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add support for field collapsing

    I've utilized field collapsing (aka result grouping) quite a bit utilizing Solr. Being able to group results together by a common element, then being able to page and sort based on that result list.

    175 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow handling spelling errors in search "Did you mean ''?"

    It would be really nice to have spell check and auto correct as part of search.

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

    134 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

  8. Support custom dictionary

    Some domestic senario like, Legal, really domestic topic require custome dictionary for more accurate wordbreaking, stemming and normalization. I think custome dictionary with easy maintemance like SharePoint or FAST provide today is help this type of senario.

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

    121 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 →
  10. 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?

    93 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. 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 →
  12. 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.

    65 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 →
  13. Implement other highlighters

    Right now only Postings highlighter is implemented, which highlights single terms instead of full phrase query. Would be good to have other highlighters.
    As said here : https://stackoverflow.com/questions/42411353/azure-search-highlights-for-phrases-with-double-quotes

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

    42 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. 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 →
  16. Disable or replace TF-IDF for relevance computing

    (Posting on behalf of Xu Lan)

    To fit the needs of our search application, we would like to change the relevance computing by disabling or replacing TF-IDF.
    Elasticsearch provides a mechanism to ignore TF-IDF: https://www.elastic.co/guide/en/elasticsearch/guide/current/ignoring-tfidf.html#ignoring-tfidf.

    35 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 →
  17. Provide ability of collection Type field to be searched against individual values separately

    For a document, where there are multiple values in its collection type column, it gives it lesser score (and hence either to come lower or may not even come in the result) to it even though the search query has matched with ONE of the values in the list COMPLETELY.

    This is because, currently Azure Search considers list of all the values provided in the collection type as a single string by concatenating all of them.
    My requirement is that if the search query (for that field) matches with any of the values in the collection, it should consider it…

    27 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 →
  18. 27 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 →
  19. 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 →
  20. Support scoring profiles on suggesters

    I think it would be valuable to expand the capabilities of suggesters. Right now, they're somewhat limited. I think it would be nice if they provided the flexibility of scoring profiles. The reason why is because sometimes, it might be nice to show the most recently added or viewed documents (i.e. Edm.DateTimeOffset) as suggestions. Other times, you may want to show the most popular, or most viewed, documents (i.e Edm.Int32). These are just two scenarios that I would like to cover with suggestions, but, I'm a bit limited.

    25 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
  • Don't see your idea?

Feedback and Knowledge Base