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. Support for 2 Billion Documents

    We have 2B very small records with relatively low QPS rate. The overhead with the crawl database alone is a massive challenge.

    135 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 →
  2. Analyzer with Automatic language detection

    Our use case is that users upload files which can be in any languages, hence we have to do language identification on the content. Each file only exists in one language, meaning we don't have multiple translations of the same file.

    For now that means we have to create one field per potential language in the index and assign them corresponding language analyzers. Then when we index the file we upload it's content to the field matching the language. Then when we add more field with the same language requirements we end up with spending a huge number of fields…

    62 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 →
  3. 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 BLG1TEMPReact_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 →
  4. 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 →
  5. asciifolding support

    I have some content that contains diacritics like Caffè, which azure search would not be able to pick up if user searches Caffe. Elastic search has asciifolding support.

    Is it possible to implement or configure somewhere? http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/asciifolding-token-filter.html

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  6. Create a Sitecore Azure Search Provider

    Sitecore comes with/supports Lucene and SOLR sitecore search providers.
    Coveo have built/supports their own Sitecore search provider.
    Could Microsoft build/support a Sitecore Azure Search provider?

    Currently are a few open source implementations, e.g. https://github.com/jscott1277/SitecoreAzureSearchProvider

    In a recent press release
    http://www.sitecore.net/about/press-and-media/press-releases/2016/07/sitecore-partners-microsoft-transform-digital-experience-at-speed-microsoft-azure.aspx
    "the two companies plan to expand their long-standing strategic alliance to enrich Sitecore’s Microsoft Azure cloud offerings over the next two years"
    Might this be included as part of that?

    16 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 →
  7. Support for parsing html/xml string content

    Many documents to be indexed already contain HTML or XML content.

    An example for us would be something like the following

    Article
    - string: Title
    - string/html: Summary
    - string/html: Body
    - string: author
    - datetime: created/updated date

    etc.

    It would be very helpful if the indexer could ignore HTML/XML/CSS/JavaScript content in the string. The current suggested alternative is to provide a surrogate field with the html tags stripped out of it and use that for the index.

    The challenge is then with hit highlighting, where we'd like to display the matching content. We'd rather not have to then find…

    7 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 →
  8. base64decode method should handle standard strings

    Azure Search indexer base64decode method should handle standard URL Safe Base64 encoded strings, and not the out-of-standard strings returned by classic System.Web.HttpServerUtility.UrlTokenEncode method, which is not even available in latest versions of the framework. This method is returning non-standard strings, as it replaces padding characters '=' with a digit indicating the number of = signs that were removed. Azure Search base64 decode method expects this non-standard strings, rather than standard URL safe Base64 encoded strings, otherwise it breaks with error: "Error applying mapping function 'base64Decode' to field 'aaa': Array cannot be null.\r\nParameter name: bytes". Which means that using JavaScript or…

    6 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 →
  9. Support character expansion - e.g., German Eszett - ß

    In .NET text searches, using InvariantCulture, if I search for Straße, I will also get results for Strasse, and vice-versa.

    Azure Search should also support that.

    5 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 →
  10. 4 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 →
  11. Create multiple data sources

    Have the option to run multiple data sources will give a extra level of performance and will avoid reinventing the wheel.

    We are working with multiple databases in Azure but we need to combine them and bring a particular result. Multiple data sources will bring the feature which allow us to actually use Search as an really advance search engine. We use DocumentDb and SQL Server in Azure, so it will be just brilliant to have that combination. The posibilities will be endless.

    3 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 →
  12. Real Time Updates

    Real time index updates would be very useful. If we can get near real time updates through the use of reserved hardware then that's probably sufficient.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Indexing  ·  Flag idea as inappropriate…  ·  Admin →
  13. Search Index definition VS Population

    When we create an index we define it with a JSON schema.
    When pushing documents into the index we have to adhere to that schema exactly.

    In our domain that JSON document may contain other attributes which are important but are not candidates for indexing. Currently we have to pull out the fields from our document and hand those on to Azure Search for indexing.

    Latency, traffic, other implications aside it would be nice if Azure Search only looked for the indexed attributes and ignored everything else.

    1 vote
    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 →
  14. Index is stuck in Creating state - unfixable!

    I can't delete an index as it is stuck in creating state. Please provide controls to force deletion of indexes which are stuck in creation state.

    1 vote
    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 →

    Hi Darryl,
    The index was stuck in Creating state due to a bug on our side – eventually we identified this “partially created” index and removed it, so you should be able to recreate this index now. Please let me know if you’re still having issues.
    I apologize for the inconvenience this has caused for you.

    Thank you for using Azure Search.
    Eugene Shvets

  15. Support more delimiters when indexing CSV blobs

    When indexing CSV blobs with Azure Search blob indexer, please add support for delimiters other than ",". We have many blobs that use | and \t as delimiters.

    1 vote
    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 →
  16. Allow posting of columns that don't exist

    When I post a document with columns that don’t exist in the index schema, it currently rejects the document. We would like the ability to post documents to the index with columns that don’t exist in the index. Of course, there is no expectation that these additional columns will be processed in any way (except perhaps returned when all columns are requested in the search query)

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

Feedback and Knowledge Base