Bruce Johnston - MSFT

My feedback

  1. 61 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Search » Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
    Bruce Johnston - MSFT shared this idea  · 
  2. 143 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Azure Search » Multi-tenancy  ·  Flag idea as inappropriate…  ·  Admin →
    Bruce Johnston - MSFT supported this idea  · 
  3. 251 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Azure Search » Indexing  ·  Flag idea as inappropriate…  ·  Admin →
    Bruce Johnston - MSFT supported this idea  · 
  4. 242 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Search » Multi-tenancy  ·  Flag idea as inappropriate…  ·  Admin →
    Bruce Johnston - MSFT supported this idea  · 
  5. 469 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  6 comments  ·  Azure Search » Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
    Bruce Johnston - MSFT supported this idea  · 
  6. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Azure Search » Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
    Bruce Johnston - MSFT commented  · 

    Thanks for the suggestion.

    Your workaround doesn’t actually give you the results you want. The query as expressed using all is matching documents where every social account is strictly either Facebook or Twitter. If any other social account is present, the document won’t match. Your workaround doesn’t have this property. A document must have *at least* Facebook and Twitter in order to match, but not exclusively those.

    You’ll find that no matter how you try to rewrite the query, you won’t be able to express an equivalent to the “all” query. This is a fundamental limitation of Azure Search due to the way inverted indexes are used to execute filters. It isn’t an unsolvable problem, but it’s very challenging and it’s unlikely we’ll address it soon unless it becomes a very highly-requested feature.

  7. 27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Azure Search  ·  Flag idea as inappropriate…  ·  Admin →
    Bruce Johnston - MSFT commented  · 

    If document scores were always in a fixed numeric range and their absolute values were meaningful, then I'd see the value in such a feature. But given that they are only meaningful relative to other scores in the same resultset, how would you ever pick a reasonable value for the minimum score? That seems fragile, especially when the range of scores can easily change by tweaking a scoring profile or adding term boosting to your query, for example.

    Is there a reason $top isn't sufficient to limit the number of search results in your case?

  8. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  (General Feedback) » Other  ·  Flag idea as inappropriate…  ·  Admin →
    Bruce Johnston - MSFT shared this idea  · 
  9. 70 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Azure Search » Indexing  ·  Flag idea as inappropriate…  ·  Admin →
    Bruce Johnston - MSFT commented  · 

    To clarify, is the functionality you're looking for this:

    geo.distance(location1, location2) lt 100

    where "location1" and "location2" are fields in the same index, or more like this:

    geo.distance(location1, POINT(-127.89734578345 45.234534534)) lt distanceField

    where "distanceField" is a numeric field in the same index?

  10. 11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Azure Search » REST API  ·  Flag idea as inappropriate…  ·  Admin →
    Bruce Johnston - MSFT supported this idea  · 
  11. 801 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  17 comments  ·  Azure Search » Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
    Bruce Johnston - MSFT supported this idea  · 
    Bruce Johnston - MSFT shared this idea  · 

Feedback and Knowledge Base