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. asciifolding support

    I have some content that contains diacritics like Caffè, which azure search would not be able to pick up if user searches Caffe. Elastic search has asciifolding support.

    Is it possible to implement or configure somewhere? http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/asciifolding-token-filter.html

    17 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 →
  2. Support startsWith, contains, and endsWith wildcard style queries

    In simple query syntax wildcard style searches are supported. OData is great with its rich query support but is missing support for wildcard style searches like simple query syntax.

    To me the easiest path for implementation would be to support the startsWith, contains, and endsWiths functions in OData.

    178 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  3. HTTP POST based search query

    I can see only HTTP GET is supported.
    Hope I don't get a 414 (Request-URI Too Long) status if a URI is longer than the server can handle

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

    Azure Search now supports invoking Search and Suggest REST APIs via HTTP POST (previously you could only invoke them using GET). This is useful in scenarios where you have large filters and/or many facets and may be constrained by the 8 KB limit on the length of request URIs.

    The new endpoints are now available in the 2015-02-28-Preview API version, documented here:

    https://azure.microsoft.com/documentation/articles/search-api-2015-02-28-preview/#SearchDocs

    https://azure.microsoft.com/documentation/articles/search-api-2015-02-28-preview/#Suggestions

  4. add extra transactions

    the 5,000 transactions are depleted in few hours, for a new website, that because of the crawling bots, i have 0 visitors on the website and all 5,000 transactions gone. The search api is useless!!!!

    123 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  5. Customize highlights

    Right now it returns matched text between <em> tags. Instead would it be possible to return it as start and end postion value pairs in a given field. We can convert the current output in that format but wanted to know if there are customization options in the service itself.

    We are finding that consuming the current format is not very useful (<em> means italics, we want to show matched text in bold and in different color) and quite heavy to render (having html controls rather than native). We are currently looking to parse the string and finding start/end index…

    2 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 →
  6. Allow posting of columns that don't exist

    When I post a document with columns that don’t exist in the index schema, it currently rejects the document. We would like the ability to post documents to the index with columns that don’t 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  7. Sort results by rank

    We had also requested sort results by rank

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

    We need to be able to support the few hundred QPS requirement without slowing down

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  9. Tag Boosting

    The idea is simple: apply a boost to a document if it matches a tag, where matching a tag means that given a field name and a value that’s part of the scoring function definition, we apply the boost if the field value equals the given value or for multi-valued fields if any of the values equals the given value.
    This allows people to tag products as “promotion” and get a generic promo boost or stuff like that.
    If we had conditions on all scoring functions, this could just be constant scoring with a condition. The scenario is so clear…

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

    We are working out the search frontend and one of the things we really would love to see is getting back a fragment of a matching search when searching on a text field.
    For example, we do a search on text, in documents that can be rather large. We don’t want to download the full message body for the 10 matching results, but it would be good if we could get the part of the document where the matching search text is found. (just like bing/google shows when searching on a term)
    Right now we retrieve all messages and then…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  11. JSONP or CORS Support

    [User 1]We would like to query the Azure Search service directly in javascript using AJAX.
    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
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  12. Control of date ranges during searches

    Allowing control of date ranges during searches

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  1 comment  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  13. API for managing star/popularity/reputation ratings

    Require API for managing star/popularity/reputation ratings

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support geolocalization / spatial search

    Queries like:


    • Records within a range of X kilometers/miles from a specific point.

    • Records within a field (multiple coordinates like a country, ... - just like polygons in google maps)

    • Order by distance

    • Support for facets

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  15. Auto-indexing of DocDB

    Lately, I've been working a lot with Cloudant, which is a distributed CouchDB platform with integrated Lucene search. I absolutely love the fact that you can define some sort of triggers that, when a document is inserted or updated, update the index to reflect that operation. Likewise, when a document is deleted, the corresponding indexes are deleted from Lucene.

    This is particularly convenient as you don't have to manually sync your DB and your search index, everything happens automatically under the cover. It would be great to have that on top of Azure Storage or the upcoming DocDB (even though…

    40 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 →
  16. Provide searching of phrases

    Without this capability, azure search may not be able to effectively search "dense" content (e.g., msw). Another example is an index I have with scientific journal docs. When I search for "back pain", the best I could do (please correct me if I'm wrong) is:

    text=back,pain&textmode=all

    Even though each query result contains "back" and "pain", most of them are irrelevant and have nothing to do with "back pain".

    Boosting the rank scoring of finding multiple adjacent terms could help but the query results would still mostly be irrelevant.

    4 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 →
  17. provide query performance feedback on request

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

    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!
    Thanks you,
    Eugene Shvets
    Developer
    Azure Search

  18. Return the number of results for each query

    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.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  19. Search Index definition VS Population

    When we create an index we define it with a JSON schema.
    When pushing documents into the index we have to adhere to that schema exactly.

    In our domain that JSON document may contain other attributes which are important but are not candidates for indexing. Currently we have to pull out the fields from our document and hand those on to Azure Search for indexing.

    Latency, traffic, other implications aside it would be nice if Azure Search only looked for the indexed attributes and ignored everything else.

    1 vote
    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 →
  20. Define target language for index

    in terms of internationalisation (internationalization), it would be great if there was a way to indicate a target language in the same way that a document type can currently be indicated when creating a full text index ie: be able to indicate that another column or attribute is holding details of the language. Auto-language detection is great but often isn't enough. What it is good for is multi-lingual documents.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Internationalization  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base