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. REST and/or PowerShell equivalent for options in the Azure portal

    For the same reason that it's good to have the script options in SSMS, it would be great to have a REST and/or PowerShell equivalent for options in the Azure portal. (It would be REALLY good to have that right across the portal but your team could take the lead on it :-))

    49 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Client SDK  ·  Flag idea as inappropriate…  ·  Admin →
  2. Datasource can contain multiple DocumentDB collections

    Because each DocumentDB collection can be only 10GB, we had to partition our data over multiple collections (app01, app02, etc..).

    When creating a indexer Data Source, the container field can only take one collection name. We can get around the problem by creating multiple indexer and multiple data source for each documentDB collection, but it would be much easier if:

    1. DataSource's container property can accept a list of names.

    or

    2. The container property can accept regex expression. So it would be something like "container" : { "regex": "[0-9]"}

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

    DocumentDB now supports partitioned collections with potentially infinite scale (see https://azure.microsoft.com/en-us/documentation/articles/documentdb-partition-data/), and Azure Search now has support for those collections as well. This obviates the need for “old-style” explicitly partitioned collections. If you haven’t done so already, please consider switching to the new DocumentDB collections.

    Thank you for using Azure Search!
    Your Azure Search team

  3. Auto-indexing of DocDB

    Lately, I've been working a lot with Cloudant, which is a distributed CouchDB platform with integrated Lucene search. I absolutely love the fact that you can define some sort of triggers that, when a document is inserted or updated, update the index to reflect that operation. Likewise, when a document is deleted, the corresponding indexes are deleted from Lucene.

    This is particularly convenient as you don't have to manually sync your DB and your search index, everything happens automatically under the cover. It would be great to have that on top of Azure Storage or the upcoming DocDB (even though…

    40 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 →
  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. Add fuzzy logic on searches

    Please allow for fuzzy searches by enable that feature on the Lucene Simple Query Parser implementation (https://msdn.microsoft.com/en-us/library/azure/dn798920.aspx). It would greatly help to people who misspell some technical words or brand names.

    35 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 →
  6. Named Entity Recognition

    Named Entity Recognition (NER) is the ability to extract entities from pieces of text. Entities can be many things but most often they are people, places and temporal derivatives.
    An implementation I have used with SolR is here https://opennlp.apache.org/documentation/1.5.3/manual/opennlp.html#tools.namefind.recognition

    I would like to see something similar in Azure Search.

    Why

    Imagine you are an investigator and you have a load of documents which potentially could yield clues. Being able to extract the entities from documents could mean being able to recognise

    Who
    Where
    When
    With Whom

    Imagine then being able to take those entities and put them into a graph…

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Enterprise  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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 →
  8. Smaller than Standard plans

    There is no emulator for Azure Search so the development needs to take place in the cloud. Free plan is too small (especially the number of indexes), and Standard plan becomes expensive very quickly when you have several developers working on the same app. Each of them would have to have a separate service so they don't step on each other toes.

    29 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 →
  9. 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 →
  10. 24 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 →
  11. Allowing custom analyzer for a field will help us deciding tokenization process

    We are using search service in industrial domain for searching some information in the plant. They follow some nomenclature for some of fields like BLG1_TEMP_React_South. In above case i want to tokenize based on underscore and camel casing because currently it is tokenized as one word and substring is not supported. Hence currently we are pre-processing this and storing in a seperate collection<string> field. But it would be nicer if custom analyzer for some field type is allowed.

    24 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 →
  12. Progressive cost for Azure search

    There is currently only two plans for Azure Search. Free 15,000 documents and Standard 15M documents at 300$/month. Need a more progressive pricing model like all other products. This is hard to justify when your search engine cost more then the hosting and storage...

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Pricing and Quotas  ·  Flag idea as inappropriate…  ·  Admin →
  13. 21 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 →
  14. Document Level Security Trimming

    An Index contains data from a source (Blob Store, SQL DB, DocumentDB, say DropBox one day?). Different sources may have different and detailed security on each document.

    We index these sources normally as a 'super-user' of some kind so the index may contain information from any indexed doc (like 'the bosses salary').

    At index query time of course the original document source is not available. It should be possible though to allow one or more 'roles' to be added to each document as it is indexed and to specify roles in the Search query.

    In this way a middleware search…

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  15. Noise Word (stopwords) List

    Noise word list (or equivalent) creation

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  16. Localization

    Multilanguage support

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Internationalization  ·  Flag idea as inappropriate…  ·  Admin →
  17. Proximity ranking

    when searching for two or more terms, give a higher rank value to terms near to each other

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Scoring  ·  Flag idea as inappropriate…  ·  Admin →
  18. SQL Azure indexer support for Collection(Edm.String)

    Currently migrating from FTS to Azure search. While in preview we setup our indexes with collections for some one to many data types (phone numbers, addresses, etc...) It would be nice to realize these collections with an indexer.. As far as the structure of the column we don't really have an existing structure in our system so we'd just build it based on what made the most sense for the way you process data.. I realize fundamentally that type of structure in SQL is unnatural so there's probably not something that just naturally fits. Possibly XML?

    Few thoughts
    -JSON (since…

    19 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 →
  19. 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 →
  20. Support for searching of part of words

    It’s hard to estimate the importance and the frequency of querying on ‘sub-word-value’, because mostly they will be entering the full word

    Querying on ‘similar’ values (stemming) is not something that is very important in our scenarios, because customers will typically search on exact values (order numbers, customer names, etc)
    Things around spaces or not can off course be handy (was the address of that customer Waterstreet, Water str. Or Water Street, for example)
    i.e.,
    https://azsearchp1.cloudapp.net/svc3/indexes/fulltexttestindex/search?text=LOFT&skip=0&take=10 NOT returning matches, while
    https://azsearchp1.cloudapp.net/svc3/indexes/fulltexttestindex/search?text=LOFT1234&skip=0&take=10 is returning matches.

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

Feedback and Knowledge Base