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. Modelling Complex Types in Indexes

    When modelling an index the data types are restrictive. There are simple types and collections. There is nothing that allows us to model complex types e.g.

    ...
    "name": {
    "first": "Ericka",
    "last": "Banks"
    },......

    The oData spec allows for complex types

    http://www.odata.org/documentation/odata-version-2-0/overview/

    1,344 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    24 comments  ·  Data Types  ·  Flag idea as inappropriate…  ·  Admin →
  2. Provide a startup-friendly billing model

    For startups it might be interesting to split billing in 2: queries and storage (similar to the Windows Azure Storage billing model).
    Our customer will have lots of records from day 1 (minimum 4 million), but the number of QPS will be very low the first weeks/months.

    So we might want to start with a shared instance in terms of QPS, but not for data / # documents.

    716 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  3. 355 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    24 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →

    This functionality is now available to all customers as a part of Cognitive Search feature of Azure Search. See:
    - Introduction to Cognitive Search: https://docs.microsoft.com/azure/search/cognitive-search-concept-intro
    - Process and extract information from images: https://docs.microsoft.com/azure/search/cognitive-search-concept-image-scenarios

    Please try it out and give us your feedback.
    Thanks,
    Your Azure Search team

  4. Blob Indexing w File Crackers

    We would love to have blob containers indexed. One option may be to use iFilter support.

    205 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  11 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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 →
  6. Azure Search and SQL Server integration

    Integrating SQL Server (Azure and on-prem) with Azure Search. A search in table/column that is Azure Search enabled would fall into a Azure Search query in the background, not visual for the developer.

    Only Azure Search enabled columns and tables would be handled by Azure Search and it would not be visible for the database consumer.

    Only a Azure Search Package that is installed on a on-prem machine that would enable the DBA to define which tables or columns that should be Azure Search enabled. Database triggers for SELECT, INSERT, UPDATE and DELETE would translate into Azure Search REST based…

    174 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 →
  7. Support for 2 Billion Documents

    We have 2B very small records with relatively low QPS rate. The overhead with the crawl database alone is a massive challenge.

    135 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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 →
  9. 106 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 →
  10. 80 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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

  12. Include search functionality

    Incorporate Lucene/SOLR or microsoft search server into appfabric to allow searching across files (table/azure storage), databases, objects cached items, etc. Allow for cost effective cloud based storage + caching.

    71 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. DocumentDB indexer should be able to index MongoDb collections

    If I create a MongoDB collection backed by DocumentDB, I should be able to use the DocumentDB indexer to ingest it into Azure Search.

    69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support user-provided query in SQL indexer

    Let's say I run an indexer to read a really large table, with a billion records, out of which I'm interested in only a few thousands. This is a database I do not own, and I have only read permissions to it.

    In this case it would be better to have a simple filter on which data to keep in the indexer throw away the irrelevant data.

    For eg: "Index this table where TeamName equals MyTeam"

    Even though the indexer runs on a large set of data, my index would only contain a smaller subset of data.

    Smaller the index,…

    66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  15. Analyzer with Automatic language detection

    Our use case is that users upload files which can be in any languages, hence we have to do language identification on the content. Each file only exists in one language, meaning we don't have multiple translations of the same file.

    For now that means we have to create one field per potential language in the index and assign them corresponding language analyzers. Then when we index the file we upload it's content to the field matching the language. Then when we add more field with the same language requirements we end up with spending a huge number of fields…

    62 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 →
  16. Add OData syntax support for startswith, contains, and endswith queries

    This is essentially a duplicate of another suggestion: https://feedback.azure.com/forums/263029-azure-search/suggestions/6470849

    The original suggestion mentioned odata support, and while it was marked as complete, it was only added to lucene searches.

    I'm sure many of the 178 votes where for specifically odata support.

    58 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 →
  17. Cover Azure Search in the HIPAA BAA

    Please add Azure Search to the HIPAA BAA so we can use it in healthcare software.

    56 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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 →
  19. Provide some sort of usage feedback (QPS)

    We need to see what is the average QPS use so we can know if we need another replica or some sort of auto-scaling so we can adjust when we hit high demand (maybe auto-scaled based on % of max QPS?).

    51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  20. Improve collection matching expressions

    Currently, collection matching only supports simple equality for the 'any' option and inequality for the 'all' option.

    I would like to be able match a collection against a set of values instead of testing a single match individually and then combining the results as shown below

    $filter=tags/any(t: t eq 'x') and tags/any(t: t eq 'y')

    Additionally, it would also be useful to have the capabilities to include simple boolean logic within the lambda to craft expressions that match a collection item against slightly more complex logic for example:

    $filter=tags/any(t: t eq 'x' or t eq 'y')

    50 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 4 5 6
  • Don't see your idea?

Feedback and Knowledge Base