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. 30 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 →
  2. allow indexers to call DocumentDB stored procedures

    We have difficulty in transferring documents where we require multiple maps of our data into the flat search index. There is a limit of two user defined functions (which we use to do this) and there doesn't appear to be a way to call a stored procedure through the query language. Having the search indexers support DocumentDB stored procedures gives us far more power and flexibility to map the data correctly. At the moment we have had to revert back to writing our own code to do this.

    30 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 →
  3. Add an API for Text extraction from a file (or string/stream with file content)

    Indexer https://azure.microsoft.com/en-us/documentation/articles/search-howto-indexing-azure-blob-storage/ does extraction of text from a file (document).
    Instead of using azure blob (extra implementation and usage charge) and delay with processing a document from there, client will have possibility to extract text from document and do mergeOrUpload content.

    We know when file content was changed (or a new file created) and would like to handle that our self.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  4. Provide a PHP SDK for Azure Search

    Provide a PHP SDK for Azure Search that covers the same functionality as the .NET SDK.

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client SDK  ·  Flag idea as inappropriate…  ·  Admin →
  5. MicrosoftLanguageStemmingTokenizer cannot process word 'F#' correctly

    'F#' is a well-known programming language, but if you tokenize sentence contains 'F#' with "en.microsoft" analyzer, it will be omitted. However, 'C#' works fine and does not have such issue.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bugs  ·  Flag idea as inappropriate…  ·  Admin →
  6. Enable indexing of gzip compressed blobs

    https://stackoverflow.com/questions/46245505/indexing-gzipped-blobs-in-azure-search

    I am trying to setup Azure Search over Azure Blob. The json blobs are compressed using gzip.

    When I try to index the blobs as-is, I get the exception :

    "Error detecting index schema from data source: "Error processing blob https://mystorageaccount.blob.core.windows.net/mycontainer/urlencodedname with content type ''. Status:UnsupportedMediaType, error:""

    Looks like Azure Search blob indexer does support indexing ZIP archives (application/zip MIME type), but not gzip-compressed files.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  7. Elastic Azure Search

    Provide an elasticity option as with Azure SQL Databases, for search it's a MUST HAVE feature!!!

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Proper support for DateTimeOffset

    Search should ingest and support a true implementation of DateTimeOffset. The current implementation merely converts an incoming DateTimeOffset to a DateTime in UTC, subsequently resulting in the loss of data, as the original offset can no longer be retrieved. The currently implementation necessitates persisting a related sidecar attribute of the original offset and subsequently requires the consumer to convert and rehydrate the property. This is exceptionally tedious, especially for use cases with several dozen DateTimeOffset attributes with varying offsets.

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Data Types  ·  Flag idea as inappropriate…  ·  Admin →
  9. Extend spatial features to allow indexing and searching of polygons and multi-polygons

    Extend spatial features to allow indexing and searching of polygons and multi-polygons

    27 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 →
  10. Provide ability of collection Type field to be searched against individual values separately

    For a document, where there are multiple values in its collection type column, it gives it lesser score (and hence either to come lower or may not even come in the result) to it even though the search query has matched with ONE of the values in the list COMPLETELY.

    This is because, currently Azure Search considers list of all the values provided in the collection type as a single string by concatenating all of them.
    My requirement is that if the search query (for that field) matches with any of the values in the collection, it should consider it…

    27 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 →
  11. clone index

    I'd like to implement 'versioning' indexes for each DocDB repository.
    In example, DocDB collections are crawler-2016 and crawler-2015, each of which will be indexed to index-2016 and index-2015 in Azure Search.

    In this operation, 'Clone Index' button could be helpful greatly as I have to create each index one by one. Actually I screen-captured previous index fields and tick-tick index checkboxes which created from DocDB import datasource.

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Portal  ·  Flag idea as inappropriate…  ·  Admin →
  12. 27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  REST API  ·  Flag idea as inappropriate…  ·  Admin →
  13. Improve Faceting accuracy by having an option to count all records

    For fields that have a large distinct value diversity, the faceting feature gives inaccurate results unless the count parameter is set to a number greater than the number of distinct values in a field. There should be an option in an index field that indicates to the search engine to count and facet all the values in a column. I realize this would hurt performance so it should be optional. But sometimes accuracy is more important than raw performance for consumers of your service.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  14. Ignore thumbnails when indexing word documents

    Word supports saving documents with a thumbnail which contains the text content from the first page. When Azure Search indexes documents, it also indexes their embedded documents. Generally speaking this is useful behaviour, but in this case it leads to content duplication of the first page.

    We cannot control documents provided by users so Azure Search should handle this and ignore thumbnails when indexing Word Documents.

    26 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 →
  15. Indexer (crawler) for Apache Cassandra API in Azure Cosmos DB

    Add an indexer/crawler for Apache Cassandra API in Azure Cosmos DB

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow access to stored term frequencies for searchable fields

    Term frequencies are maintained for searchable fields in order to compute things like TF/IDF quickly. It should be possible to access those term frequencies for additional analysis.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Given the current API surface area of Azure Search, how would you actually use these term frequencies? Said another way, what other capabilities would you require in the API in order for term frequencies to actually be useful?

    Thank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.

    Thanks,
    Mike Carter
    Azure Search Product Team

  17. Support for Postgresql for using indexers

    Please provide support for ingesting data from PostgreSQL, similar to the existing support for Azure SQL Database.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  18. Implement Data Lake Gen2 Search Indexer

    It seems like MSFT is pushing Data Lake as a more robust implementation of Azure Blob.

    Implementing a Data Lake Gen2 Search Indexer would give my team confidence that Azure Search will align with our move to Data Lake.

    23 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 →
  19. 22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Scoring  ·  Flag idea as inappropriate…  ·  Admin →
  20. OpenSearch support for search federation

    Many companies use SharePoint as their entry point for search but federate actual searching across other data stores/sources.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Enterprise  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base