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
-
Modelling Complex Types in Indexes
When modelling an index the data types are restrictive. There are simple types and collections. There is nothing that allows us to model complex types e.g.
...
"name": {
"first": "Ericka",
"last": "Banks"
},......The oData spec allows for complex types
http://www.odata.org/documentation/odata-version-2-0/overview/
1,190 votesWe are ready to onboard more customers who are interested in participating in the private preview of Complex Types. If you’re interested, please contact us at azuresearch_contact@microsoft.com.
Please note that the private preview of Complex Types is only accessible via the REST API. We are working on .NET SDK support for the Public Preview.
Also, if you get an error message when you email azuresearch_contact, don’t worry — we are receiving your requests and will reply to you individually.
Thanks!
-
Allow customer to provide encryption key for indexed data
To meet enterprise security requirements, it would be great if index data could be encrypted (ideally with a key provided by the customer.)
139 votesThank you for your feedback. We’ve started working on this for an upcoming release of Azure Search.
Thanks,
Elad
Azure Search Product Team -
Indexer for Azure File shares
Index Azure File shares similar to blobs
101 votesPrivate preview of this feature is now available.
If you’re interested in participating, please email azscustquestions@microsoft.comThanks,
Azure Search team -
Improve collection matching expressions
Currently, collection matching only supports simple equality for the 'any' option and inequality for the 'all' option.
I would like to be able match a collection against a set of values instead of testing a single match individually and then combining the results as shown below
$filter=tags/any(t: t eq 'x') and tags/any(t: t eq 'y')
Additionally, it would also be useful to have the capabilities to include simple boolean logic within the lambda to craft expressions that match a collection item against slightly more complex logic for example:
$filter=tags/any(t: t eq 'x' or t eq 'y')
46 votesWe are currently working on expanding the filter syntax available inside lambda expressions (‘any’ and ‘all’). This work is part of the work on Complex Types (currently the highest-voted User Voice item for Azure Search).
Regarding the specific examples in this post, the second example is now possible using the new search.in function. For example, this:
$filter=tags/any(t: t eq ‘x’) or tags/any(t: t eq ‘y’)Can now be written like this:
$filter=tags/any(t: search.in(t, ‘x,y’))In the future we will also be directly supporting ‘or’ inside any/all. We will also support ‘and’ inside any/all for complex types and some primitive types, but not for collections of strings, so the example in the post above using ‘and’ will still be the only way to write that particular query.
The ETA for these filter syntax changes is the same as for Complex Types, since we are delivering them together. See this post for…
-
27 votes
The feature is available as a preview in our latest preview API.
For more details, please look for ‘moreLikeThis’ search parameter on https://azure.microsoft.com/en-us/documentation/articles/search-api-2015-02-28-preview/
-
Please provide support for MySQL database for pushing data to the index from azure portal
Please provide support for MySQL database for pushing data to the index from azure portal
23 votesThis feature is currently in private preview (REST API support only, not portal support yet). For onboarding instructions, please email Victor Liu (victliu at the usual Microsoft domain)
-
It would be very useful, for the sake of more accurate suggestions, to provide the equivalent of SolR ShingleFilterFactory. This would let u
It would be very useful, in order to provide more accurate suggestions, to have the equivalent of SolR ShingleFilterFactory (http://lucene.apache.org/core/4_7_0/analyzers-common/org/apache/lucene/analysis/shingle/ShingleFilterFactory.html).
This would let us give the user suggestions with actual groups of words found in the index.17 votesPlease take a look at the autcomplete API and let us know if this suits your needs. This API is currently in preview.
Link: https://docs.microsoft.com/en-us/rest/api/searchservice/autocomplete
-
Make errors and warnings as helpful and constructive as possible
Please try not to provide cryptic error and warning statements that are only understandable by project developers but rather try to provide HELPFUL and CONSTRUCTIVE errors and warnings that more quickly help the poor user.
I'm a newbie who quickly encountered the error:
400: {"result":{"Message":"Missing request parameters: definition"}}
when I tried to create a new index without a fields element. Why couldn't it provide (it certainly "knows" what the problem is) a more helpful, constructive error like
400: {"result":{"Message":"Missing required fields element when creating a new index"}}
11 votesWe are taking this feedback and working to improve our messages.
-
Populate json string in Azure SQL table directly into Azure Search Index such that it is queryable on json attributes
I have a column in my Azure SQL table that contains json (not array of strings) is there a direct way to populate that into azure search index so that it is queryable (filterable on the json attributes)
7 votesWe’re working on this feature that will also compose with the “complex types” feature (https://feedback.azure.com/forums/263029-azure-search/suggestions/6670910-modelling-complex-types-in-indexes) that’s already available in private preview.
If you’re interested in trying this out, you can email azscustquestions@microsoft.comThanks,
Your Azure Search team -
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.
4 votesWe have started working on this and aim to have VNet support in the first half of CY 2019.
-
Retrieve index data source
Once the data source is created there is no current method to identify where the index is indexing the data from. It would be nice to know where the data is coming from, like is it a QA, DEV or PROD, or is it a blob storage account, sql server, documentDB, etc.
I don't need the actual connection string or password or sensitive info, just the repository name would be great.
2 votesWe’re adding ability retrieve a “sanitized” connection string (without keys and passwords) via GET datasource API, and will show this info in the portal.
- Don't see your idea?