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. 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 →
  2. Support for searching of part of words

    It’s hard to estimate the importance and the frequency of querying on ‘sub-word-value’, because mostly they will be entering the full word

    Querying on ‘similar’ values (stemming) is not something that is very important in our scenarios, because customers will typically search on exact values (order numbers, customer names, etc)
    Things around spaces or not can off course be handy (was the address of that customer Waterstreet, Water str. Or Water Street, for example)
    i.e.,
    https://azsearchp1.cloudapp.net/svc3/indexes/fulltexttestindex/search?text=LOFT&skip=0&take=10 NOT returning matches, while
    https://azsearchp1.cloudapp.net/svc3/indexes/fulltexttestindex/search?text=LOFT1234&skip=0&take=10 is returning matches.

    17 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. Ensure data types are consistent with other Microsoft datatypes

    I presume my concern is that almost every Microsoft product seems to have a different set of supported data types and often the same name means different things in different products. In general we've been trying to get people to avoid using "money" in SQL Server and to use "decimal" instead. Similarly I presume that "text" is just a generic name for a bunch of characters but given that it's also the name of a data type that we're trying to move people away from in SQL Server

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Data Types  ·  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. 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 →
  10. 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 →
  11. 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

  12. 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 →
  13. Real Time Updates

    Real time index updates would be very useful. If we can get near real time updates through the use of reserved hardware then that's probably sufficient.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  14. 4 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 →
1 2 3 4 6 Next →
  • Don't see your idea?

Feedback and Knowledge Base