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. 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

  2. Allow custom defined Field Mapping Function

    Currently when defining the indexers, one can specify the field mappings from source to target fields. Only a limited set of functions such as Extract token at position etc are supported. It would be desirable to support Func syntax such that each row is passed onto the func which then decide the target field value based on developer defined logic in func.

    Eg: we have a cosmo db source and a azure table storage data source. The partition key for cosmo db collection is combination of tenantId:studentId for efficient read/writes across partitions based on our data. The azure table storage…

    15 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 →

    We recently introduced a capability of Azure Search that we call Cognitive Search.

    Cognitive Search allows you to apply enrichment and transformation steps to your data that we call Cognitive Skills. You can select from predefined skills or apply your own custom skill.

    The best way to transform your input data when you want to define your own function would be through a custom skill that you run as part of your enrichment pipeline.

    You can read how to do this at https://docs.microsoft.com/en-us/azure/search/cognitive-search-custom-skill-interface

    Thanks!
    -Luis Cabrera

  3. 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 →
  4. Blob Indexer should continue indexing documents after encountering an error

    This is related to...

    https://feedback.azure.com/forums/263029-azure-search/suggestions/11628435-blob-indexer-should-be-able-to-skip-unsupported-co

    ...whilst a change has been added to easily configure the indexer to exclude unsupported document formats, this is inadequate. Bugs in the indexer and corrupt documents are going to ensure that there will always be a percentage of documents that can't be processed by the indexer. This shouldn't stop the indexer from processing data it can index.

    When the indexer encounters an error processing a document it should log the error then proceed with indexing of the rest of the documents in storage.

    A run shouldn't be halted until the indexer has attempted to index…

    34 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 →
  5. Smallint and Tinyint not recognized as integral types for SQL Server deletion detection

    I've been trying to create an auto indexer over a view. The column I want to use for deletion detection is type Tinyint, but the indexer throws an error saying this isn't an integral type.

    I've also tried with smallint, but it only seems to accept int and bigint.

    1 vote
    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 →
  6. Support add-ins for custom file types (e.g. DICOM)

    Would like to have DICOM files indexed for search in the Azure Portal. Support for adding custom logic for parsing arbitrary file types would be sufficient.

    6 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 →

    This functionality is now available to all customers as a part of Cognitive Search feature of Azure Search, using “custom skills”. See:
    - Introduction to Cognitive Search: https://docs.microsoft.com/azure/search/cognitive-search-concept-intro
    - Integrate custom skills: https://docs.microsoft.com/en-us/azure/search/cognitive-search-custom-skill-interface

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

  7. 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 →
  8. 25 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 →
  9. 2 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 →
  10. 18 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. Support shared access signature for blob datasource credentials

    Currently, blob datasource requires a full connection string. Sometime, specifying a SAS container URL is preferable.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support indexing of append blobs

    It seems Azure Search doesn't currently work with append blobs. We use append blobs for logging and Azure search would help a lot if it could handle the blobs.

    1 vote
    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 →
  13. Allow SkipContent to be set directly on the blob indexer

    The azure blob indexer currently checks for a metadata property AzureSearch_SkipContent to skip the processing of the content. It would be easier to just tell the indexer directly to skip processing content for all blobs.

    15 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 →

    This functionality is now available in REST API, using 2015-02-28-Preview version.

    Excerpt from the docs:
    Using indexer parameters to control document extraction

    If you want to skip content extraction for all blobs, you can do this using indexer configuration object, instead of having to add custom metadata to each blob individually. To do this, set SkipContent configuration property to true in the parameters object:

    PUT https://[service name].search.windows.net/indexers/?api-version=2015-02-28-Preview
    Content-Type: application/json
    api-key: [admin key]

    {
    … other parts of indexer definition
    “parameters” : { “configuration” : { “SkipContent” : true } }
    }

    Thanks!
    Your Azure Search team

  14. Extract document structure from JSON blobs

    Currently, blob indexer extracts entire document into a single 'content' field. Instead, we want the blobs containing JSON documents to be interpreted as documents with multiple fields.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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 →
  16. blob index

    How does the Azure Search Blob Indexer work with billions of blobs? The only feasible way is if it can query the Blob Service to enumerate all the blobs with a LastModified timestamp greater than the last time that the indexer was run. But the Blob Service does not support any such filter (grr why not?!). So how does Azure Search Blob Indexer work? The transaction cost for enumerating billions of blobs would be large.

    Perhaps Azure Search Blob Indexer relies upon that "hack" of using Blob Service logging to detect when blobs are updated. But logging is described in…

    4 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 →

    Hi,

    Please post questions about Azure Search on StackOverflow or our MSDN forum (https://social.msdn.microsoft.com/Forums/en-US/home?forum=azuresearch) to ensure quick response.

    A single blob indexer (or even a single search service) is not going to cope with billions of documents, due, among other reasons, to scalability limits on enumerating blobs as you note below.
    Our advice for scaling blob indexing is to provision multiple datasource/indexer pairs all writing to the same index (with datasources potentially pointing to different storage containers or storage accounts).
    Make sure your search service is scaled to run multiple indexers concurrently; keep in mind that one search unit can run one indexer at a time.

    Hope that helps!
    Your Azure Search team.

  17. 2 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 →
  18. Add facial recognition to blob storage file indexer capabilities

    Based on the facial recognition technology used in Windows Photo Gallery provide indexers with the ability to perform some form of facial recognition.

    3 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 →

    We recently released this in “public preview” as part of “Cognitive Search”. Essentially you can select an analyze image skill to identify well known faces (such as celebrities).

    You can see a demo of this at https://www.youtube.com/watch?v=Wh5Dt8wnEhg

    Also, if you want to create your own custom face recognition model, you could train a model using the Cognitive Service Face API, and then call that from a “custom skill” — see an example of how to create a custom skill here:

    https://docs.microsoft.com/en-us/azure/search/cognitive-search-create-custom-skill-example

    Thanks!

    Luis Cabrera
    Azure Search Product Team

  19. Allow indexer data source to use custom schema for SQL Azure

    Today we HAVE to use dbo schema for source tables used as data sources by the search indexer. As you know, a lot of enterprises have rules against allowing objects to be created on dbo. This seems like a unnecessary requirement, and surely this could be a simple fix, right? Just let me specify whatever level of qualifier for the container name of my object in SQL Azure...

    6 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 →
  20. 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 →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base