Azure Search: started (11 ideas) – Customer Feedback for Microsoft Azure

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

How can we improve Azure Search?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

When an admin closes an idea you've voted on, you'll get your votes back from that idea.
You can remove your votes from an open idea you support.
To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".

Enter your idea

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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/

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')

started ·

AdminThe Azure Team on UserVoice (Product Owner, Microsoft Azure) responded

We 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…

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.

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"}}

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.

Azure Search

Give feedback

Azure Search

How can we improve Azure Search?

There are two ways to get more votes:

Modelling Complex Types in Indexes

Allow customer to provide encryption key for indexed data

Indexer for Azure File shares

Improve collection matching expressions

Please provide support for MySQL database for pushing data to the index from azure portal

Provide More Like This document similarity feature

It would be very useful, for the sake of more accurate suggestions, to provide the equivalent of SolR ShingleFilterFactory. This would let u

Make errors and warnings as helpful and constructive as possible

Azure Search deployed within Virtual Network

Populate json string in Azure SQL table directly into Azure Search Index such that it is queryable on json attributes

Retrieve index data source

Feedback

Azure Search

Feedback and Knowledge Base

Searching…

Give feedback

Microsoft Azure

Your password has been reset