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. Azure Table Indexer Data Source Definition should allow specific select column options along with specifying filters

    When defining datasource of Type Azure Storage Table in the Query field, only options in the examples I see is like (PartitionKey eq '0') or something like that, but there is no example which would allow us to select columns along with the filter conditions.

    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 →
  2. Indexer priority

    We are using CosmosDb as our DB for apps search and we need to have overrides to change apps metadata on-the-fly. This allows us to hide some apps from clients or change privacy statements without the need for the developer to re-upload their work.

    To achieve this, we use a CosmosDb collection for the app data and another for the overrides.
    In order to provide our clients with search, we use Azure Search and to keep indexes up-to-date, we wanted to use Indexers.

    It is indeed possible at the present time to have multiple data sources get uploaded to the…

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

    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.

    Also, you may want to start a stack overflow discussion on this topic… may be we can think of other mechanisms (besides indexer priorities) that allow you to get to an acceptable outcome.

    Thanks,
    Luis Cabrera
    Azure Search Product Team

  3. Support picking existing index when creating an indexer in Azure Portal

    Today is only possible to create an indexer if you follow the entire process through import data workflow:

    -Select the data Source
    -Add Cognitive skills (optional)
    -Create an Index
    -Create an Indexer

    However, there are times we want to set a different schedule for an indexer or create a new one, without recreating the index.

    41 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. Use Webhooks after running an indexer

    It would be interesting if an indexer could use Webhooks to notify that it has finished indexing. In this way, for example, we can integrate it with Azure functions and avoid having to poll for the status of an Indexer that I have triggered.
    I'm working on an application that will create contents and place them in Blob Storage. An indexer will be executed and I would like to execute some searches once the indexing is done. It would be nice if the Indexer could notify a function (via a webhook) that it finished indexing in order to execute those…

    12 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 →
  5. 111 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 →
  6. Increase Blob Indexer file size limits

    The "Blob indexer: maximum characters of content extracted from a blob" limit seems rather restrictive, 32K for free, 64K for standard and 4MB for everything else. Plus when this limit is reached all you see in the azure portal is

    [{ "key": null, "message": "Truncated extracted text to 32768 characters." }]

    It'd be useful to know which documents are affected.

    37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  7. Provide field mapping function to inject a constant value into the index

    I'm creating an index which is importing data from a SQL Server Database. I would like to add a field to the index whose value is just "OK" for every document. This field does not exist in the database and we do not want to add it there.
    Is it possible to add a hard-coded field to an Azure Search index which auto-populates with the given string (in this case, "OK") for all documents that get imported?

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    need-feedback  ·  2 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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 →
  9. 62 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 →
  10. 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 →
  11. Table Storage Indexing of multiple tables at scale

    I believe that a good pattern for Azure Table Storage is to enable fast deletes by simply dropping tables. I've implemented a multi-tenant model for my data using a table per tenant, and would like to aggregate search data across tables.

    The current recommendation is to create an indexer per table. This means the number of tenants I support (which I'm hoping to be in the thousands) is limited to the number of indexers I can create, which is a very low number.

    The latest table storage SDK has methods to asynchronously list tables in a segmented fashion using continuation…

    14 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 →
  12. Support for indexing multi-line JSON files

    Support for indexing multi-line JSON files (https://en.wikipedia.org/wiki/JSON_Streaming). Currently blob indexer extracts entire json file as one document.

    It would be also nice to pair this with the gzip support so that it will be able to index *.json.gz files

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

    26 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 →
  14. Support indexing JSON-LD embedded in HTML documents

    Support indexing structured data (e.g. schema.org) in HTML documents.

    6 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 →
  15. support a mix of JSON and non-JSON blobs in the same data source

    Support a mix of JSON and non-JSON blobs in the same data source

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

    Thank you for your feedback. More information is needed before we can take action on this request.

    Assuming we find a.json and b.txt in the same data source, let’s say blob storage. Are you expecting the content of b.txt to end up in the content filed, and the fields of a.json to end up wherever they end today? Or other behavior?

    Thanks,
    Luis Cabrera
    Azure Search Product Team

  16. Run multiple Indexers at once

    We have many indexes with matching indexers that scan SQL Server tables to import/update data.

    I found that during the initial import of a new large index (millions of records, taking several hours), none of the other indexers on the same service are run at all. This means that just by adding a new index, all other indexes will become stale until the large index is finished!

    Please add the ability for multiple indexers to run simultaneously.

    54 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 →
  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. Add support for indexing PDF Custom meta data

    PDF Files allow custom meta data fields. In an archive it is good practice that the meta data is not separated from the document and hence we use the custom fields. We do however want to be able to search our archives don't want to have to write custom extractors to add the meta data to the index

    11 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 →
  19. Add xpath syntax to promote out interesting values from source [XML] documents to predefined index fields

    I have lots of structured blobs (XML, JSON), I would like a mechanism to promote/extract a given field so it can be present in a specified index field rather than just rely on text in the content field? Or must I still run an external process to parse and write these promoted values instead of using built-in Azure Search features and the Data Source / Import process?

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add support for using Azure Data Lake with blob indexer or new indexer

    Customer would want to use ADL as a centralized store and then use various services like Azure Search, HDInsight on top of the same document store

    83 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Crawlers  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base