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. Data security based on Gremlin graph API

    Currently security data filtering seems just to be possible based on e.g. a group attribute and checking users group membership using oData filter expressions. When using CosmosDB Gremlin APIs the data is organized as vertices and edges, therefore the security filtering of search results should also be made possible based on Gremlin / subgraph expressions, not only based on oData filter expressions, ideally a possible combination of both. As an example consider a Graph: story (vertex) - belongs to (edge) - group (vertex) - has (edge) - members (vertices) ...and users should only find stories of THEIR groups (which they…

    3 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 →
  2. Translation missing on Azure Search portal

    On the index field management page (Search Service > Index > Field) on Azure portal, we see some miss translation "検索可能" attribute in Japanese from "SORTABLE" attribute. It's too difficult to understand because the fields also have "SEARCHABLE" attribute which translated to "検索可能" attribute.
    See the enclosed parts on the attached screen shots both Japanese and English.
    My understanding is we should translate "SORTABLE" attribute as "ソート可能" one in Japanese.

    2 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. For the batch requests, leverage multipart content-type

    For the batch requests (Index Population APIs), leveraging the multipart content-type (http://www.w3.org/Protocols/rfc1341/72Multipart.html) would be more meaningful.

    2 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 →
  4. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →

    While the OCR should not take that long, I think what you are saying is that indexers that require a bit of processing don’t index too many documents in a given time period (1 hour).

    We are looking for mechanisms to improve throughput in our enrichment pipeline at this time. Thanks for the feedback!

    -Luis Cabrera
    Azure Search Product Team

  5. Drill down into queries

    When looking at queries, while I'm interested in full queries such as "purple shoes" and "red blazers", I'd also like to see an index of the individual words that are used in the search terms, plus the ability to drill into the query list ie: which queries contained the word "blazer"? It doesn't have to be in the UI, as long as it's downloadable. (Ideally, it would be downloadable using REST-based queries and/or OData, and be consumable by Excel/Data Explorer in Excel/PowerPivot/Tabular data models in SSAS).

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
1 2 3 5 Next →
  • Don't see your idea?

Feedback and Knowledge Base