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
-
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 votesAzure Search now supports ASCII folding with “standardasciifolding.lucene” analyzer. You can learn more here: https://msdn.microsoft.com/en-us/library/azure/dn879793.aspx
Eugene Shvets
Developer
Azure Search -
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 votesAn Azure Search provider is available on the SiteCore makertplace.
Link: https://marketplace.sitecore.net/Modules/S/Sitecore_Azure_Search_Provider.aspx?sc_lang=en
-
Support for Geography SQL Server column
Actually, the indexer returns an error if the view or the table contain a geography column, because indexer doesn't support it
15 votesThis is now available for use on columns of SQL geography Point type.
Please give it a shot and let us know if you have any feedback or encounter any issues.
Thanks!
Eugene Shvets
Azure Search -
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 votesWe 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 -
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 votesThis functionality is now available in REST API, using 2015-02-28-Preview version.
Excerpt from the docs:
Using indexer parameters to control document extractionIf 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 -
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 votesSAS credentials are now available for blob and table storage. See https://docs.microsoft.com/azure/search/search-howto-indexing-azure-blob-storage and https://docs.microsoft.com/en-us/azure/search/search-howto-indexing-azure-tables respectively for details.
Thank you for your feedback and for using Azure Search!
Your Azure Search team -
Permit bulk loading of documents from SQL server
We have about 2.5 million documents, currently stored in a table in a SQL database on Azure.
We would like to insert these documents into an Azure search service, hosted in the same datacentre.
Currently the only way to do this is by reading each row and inserting using the REST API.
Something like the request feature "Azure Search and SQL Server integration" would help in this case.
Although that request is asking for the data to be stored in SQL, in our case we want the data to be moved from SQL.
An alternative is for the REST API…
12 votesWe do have a batch API, that allows you to upload multiple documents to Azure Search. There is some more information on batching here: http://msdn.microsoft.com/en-us/library/azure/dn798930.aspx
Also, we are looking at ways of providing tighter integration with Azure SQL databases.
-
Expose search quality metrics like CTR (click-through rate) in the Search Traffic Analytics dashboard
That would require collecting information about user clicks. The dashboard could also show the number of unique users over time and MRR (mean reciprocal rank).
12 votesPlease take a look at the search traffic analysis and let us know if this suits your needs.
-
extend scoring profile to support list
As described in this link
http://stackoverflow.com/questions/27117663/azure-search-scoring-profile-on-list11 votesTake a look at the tag boosting feature of scoring profiles. This may suit your needs.
-
10 votes
Indexers can now be managed in the portal.
Thanks!
Eugene Shvets
Azure Search -
Able to do simple search on portal
To be able to view index and count of documents is what we have today. We are not able to see the actual documents also.
Can we have a simple search bar for the respective index to search on ?
This way we don't have to either write our calls to api, or use fiddler etc tools. To have this capability handy on portal itself, will be benevolent in terms of testing, verifying data upload etc.10 votesThanks for the suggestion! We’ve built a search explorer in the portal. Try it out and let us know what you think. https://pbs.twimg.com/media/CUOEEuHUwAAEQsG.jpg:large
-
Ability to index more than 1M documents in Basic
I have a basic account for $40\month, and have 1.1M documents. But I'm not able to add an additional partition. My only options are a) limit my documents to 1M (what's the point?) or b) upgrade to Standard which supports 15M documents (overkill) for $250/month?!? Of course, I could sign up two basic accounts for less, but then have to write specific code to query two search accounts. Please add the ability to add more partitions to the Basic Tier.
9 votesThis has been delivered for all services created after November 2017.
Link for more info: https://docs.microsoft.com/en-us/azure/search/search-limits-quotas-capacity
-
Make it so SearchMode=All matches if stop words are present even when querying across multiple analyzers
Not all of the documents in our corpus are localized so we must search the default language (English) and the user's locale with the provided user query. Queries that contain a stop word for either default or user language analyzer causes no results to be returned.
Example:
The documents contain 2 searchable fields (plus an ID field).
Title_EN -> English Analyzer
Title_ES -> Spanish AnalyzerA document exists with the following values:
Title_EN -> "The best document"
Title_ES -> "Un documento excelente"When a user inputs a query, we search on Title_EN and Title_ES. If the user provides the query…
9 votesIt sounds like you want to be able to control the stop words. If this is the case, please take a look at custom analyzers (https://docs.microsoft.com/en-us/rest/api/searchservice/custom-analyzers-in-azure-search). If that is not the case, I highly recommend you open this as a question in StackOverflow tagged as Azure Search (https://stackoverflow.com/questions/tagged/azure-search )
-
wildcard sql query for node.js mobile services
I want to be able to query using wildcard like so, [foo like '%?%', 'bar']
I can't do this in node js on azure mobile services.Please add this. I can't add search feature on my app without this.
9 votesHi Wil, Azure Seach is now able to index Azure SQL tables. See http://azure.microsoft.com/en-us/documentation/articles/search-howto-connecting-azure-sql-database-to-azure-search-using-indexers-2015-02-28/ for more details.
We hope this will unblock your mobile search scenario. If you have additional ideas for improvements, please let us know!
Thank you,
Eugene Shvets
Azure Search -
configurable (or unlimited) hit highlights
Per https://docs.microsoft.com/en-us/rest/api/searchservice/search-documents "Azure Search returns only up to 5 highlights per field. This limit is not configurable" >> this should be changed. Either by offering a configurable threshold, by pagination or any other way. We'd need to be able to access all hit results and not just a partial subset
9 votes -
Get documents from an array of IDs
an equivalent feature to that of the Ids Query in Elasticsearch (https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-ids-query.html) to retrieve all documents whose Ids appear in a provided array of Ids.
9 votesPlease take a look at the search.in clause in the filter parameters of the Azure Search REST API. This should be what you are looking for, but please let us know if you have any additional feedback.
Link: https://docs.microsoft.com/en-us/rest/api/searchservice/odata-expression-syntax-for-azure-search
-
Enable gzip compression
I'm adding fairly large documents via the rest API in fairly large batches. Being able to compress the JSON content seems like it would have a large impact on my ability to upload 10's of millions of documents more efficiently. Gzip for the response would be nice as well as there are times I wan't to get a large resultset in my response.
9 votesAzure Search now supports gzip compression.
-
Most common searches by Analytics
PowerBI can parse the Analytics data to obtain the "Most common search queries".
It'd be awesome if the REST API could provide this information too.7 votesYou can use the Search Traffic Analytics (https://docs.microsoft.com/en-us/azure/search/search-traffic-analytics) feature to accomplish this.
Thanks,
Vinod
Azure Search Product Team -
Allow specifying query time analyzer
Issueing a query with searchMode=all against multiple fields that use different analyzers may lead to unexpected results.
Let’s take an index with two fields where one is analyzed with English Lucene analyzer, and the other with standard (default) analyzer.
{
"fields": [
{"name": "docId", "type": "Edm.String", "key": true, "searchable": false},
{"name": "field1", "type": "Edm.String", "analyzer": "en.lucene" },
{"name": "field2", "type": "Edm.String" }
]
}Let’s add these two documents:
{
"value": [
{
"docId": "1",
"field1": "Waiting for a bus",
"field2": "Exploring cosmos"
},
{
"docId": "2",
"field1": "Run to the hills",
"field2": "run for your life"
}
]
}…
8 votesUsers can now set search and index analyzers independently
-
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 dateetc.
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 votesHi, this is now possible using the new blob indexer feature. For more details, see https://azure.microsoft.com/en-us/documentation/articles/search-howto-indexing-azure-blob-storage/
Thanks,
Azure Search team
- Don't see your idea?