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. Storage Optimized tier in the Basic tier pricing range (L0)

    For a small business with low traffic and data just over the 2GB limit of the Basic tier it´s really hard to justify to upgrade to standard tier for 3.3x more cost. The performance and scaling for Basic tier is more the enough but the 2GB limit is just to low.
    It would be nice if you could introduce storage optimized layer(L0) for the lower end of the price range where performance and scaling is not important but the storage amount is more than 2GB.

    108 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 →
  2. 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 →
  3. Extract text in a readable manner for pages using landscape orientation in PDF

    There is a known issue with PDFs that display certain pages with text oriented in a vertical manner. The issue is not that the text is not extracted, but rather that it is extracted in an unreadable manner since current extraction methods expect text to be horizontal. Unfortunately there is not currently a work around within Azure Search.

    We would need to inspect thousands of documents and rotate the vertical/landscape pages of the PDF manually before it can work as expected.

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

    13 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

  5. 2 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 →
  6. Support correlated search on complex collections

    Now that Azure Search supports complex types, it would be useful to be able to combine full-text search and strict Boolean filters when querying over complex collections. Currently this is not possible -- search.ismatch()/ismatchscoring() are not allowed in lambda expressions, and using sub-fields of complex collections in full Lucene queries has uncorrelated semantics.

    For example, if you want to search for hotels that have deluxe rooms with city views, none of these gives you exactly what you want:

    search=Rooms/Description:(city views) AND Rooms/Type:(Deluxe Room)

    search=Rooms/Description:(city views)&$filter=Rooms/any(room: room/Type eq 'Deluxe Room')

    $filter=search.ismatchscoring('city views') and Rooms/any(room: room/Type eq 'Deluxe Room')

    Instead, what you'd…

    10 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 →
  7. Highlight search text on blob documents

    search API should return document that should highlight search text inside the document. So that when i download view the document it should highlight search terms/text in documents like pdf, excel,word and etc.

    same like JFK it will do only for image but good to have document highlighting

    13 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 →
  8. Efficient way to express a true “all”

    Query with any on properties of types Collection is very easy:
    $filter=SocialAccounts/any(x: search.in(x, 'Facebook,Twitter'))

    However if you want to do the same with all you need to do something like which is not that beautifull:
    $filter=tags/any(t: t eq 'Facebook') and tags/any(t: t eq 'Twitter')

    Please implement something like:
    $filter=SocialAccounts/all(x: search.in(x, 'Facebook,Twitter'))

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Query - Search  ·  Flag idea as inappropriate…  ·  Admin →
  9. More descriptive errors for incorrect datatype

    We have been getting the following error when indexing

    The request is invalid. Details: parameters : An unexpected 'PrimitiveValue' node was found when reading from the JSON reader. A 'StartArray' node was expected

    It would be nice to know what field it failed on in the response and even better which specific object it was trying to work with and the value on that field.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Lack of features

    The azure search seems to lack many fundamental features. Ability to rename the index, clone the index are a few to name.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Support a DFS Query Then Fetch Search Type

    Support DFS Query then Fetch search type in order to get more accurate scores across shards. (Equivalent to search_type=dfs_query_then_fetch in Elasticsearch.)

    https://www.elastic.co/blog/understanding-query-then-fetch-vs-dfs-query-then-fetch

    https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-search-type.html

    6 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 →
  12. Azure Full Search with wildcard or fuzzy search not returning expected result

    Hello,
    I have following records in my Azure Search Index
    {
    "customerId": "8feda7ca-c9f0-40d9-86d8-434b0bbe94c2",
    "registeredName": "TeamPeacock",
    "tradingName": "TeamPeacock",
    },
    {
    "customerId": "b445eb04-8d07-4708-a197-770cda3a459e",
    "registeredName": "TeamPeacock1",
    "tradingName": "TeamPeacock 1",
    }

    I am using Full Search with wildcard/fuzzy search to fetch records.

    Below search queries fail to fetch the above records:
    Failed Query 1:
    {
    "search": "(peacock*) OR (peacock*~) OR (peacock~)",
    "queryType": "full",
    "searchMode": "all"
    }

    Failed Query 2:
    {
    "search": "(peacock*) OR (peacock*~) OR (peacock~)",
    "queryType": "full",
    "searchMode": "any"
    }

    Failed Query 3:
    {
    "search": "(peacock*)",
    "queryType": "full",
    "searchMode": "any"
    }

    Failed Query 4:
    {
    "search": "(peacock*~) OR (peacock~)",
    "queryType": "full",
    "searchMode": "any" …

    2 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 →
  13. Allow changing of attributes of a field once data has already been indexed

    Common attributes users want to change are type (like int to string), doc-values, stored, indexed etc.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Provide a Java SDK for Azure Search

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

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Azure search Suggestions dose not filter duplicate items

    Azure search Suggestions dose not filter duplicate items. This is Suggestions official document https://docs.microsoft.com/en-us/rest/api/searchservice/suggestions.

    Please remove useless duplicate items. Duplicate items are useless in "search-as-you-type" scenario.

    6 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 →
  17. Cognitive search indexer across many containers

    Our solution currently uses separate containers to store client files etc.
    This was decided so we could define a strong boundary for client info.
    We have around 3000 containers at the moment.

    We would like to be able to use cognitive search across all the containers, at the moment it seems like a separate data source is needed per container.

    Thanks

    3 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 →
  18. Azure Search deployed within Virtual Network

    I would like suggest Azure Search could be deployed in virtual network so that not expose the search service endpoint to internet.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  19. Include parquet files

    We store most of our data in parquet format and currently use a custom indexer on another platform to keep them indexed.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Index blob container metadata

    We're trying to set up an indexer for groups of related blobs (e.g. multiple formats of a single image file) using containers. Unfortunately, it seems like the blob indexer doesn't extract metadata from containers - only the blobs themselves. As a workaround, we can duplicate metadata across all blobs in a container, but it would be nice if the indexer supported indexing container metadata directly.

    6 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 →
← Previous 1 3 4 5 11 12
  • Don't see your idea?

Feedback and Knowledge Base