Max Melcher

2 minute read

Today I released the next version of the AzureSearchTool (v.0.3.0.0).

If you have not read about the tool at all, please see the introduction here.

In the very first version the tool was quite simple and most of the search parameters were not handled. That has changed now:

Index

I implemented the schema overview (actually that was not that much but looks great):

Index Schema and Statistics

Index Schema and Statistics

So now you can see what fields of what type you have – and how those fields are specified.

Below of the Schema you get the two available statistics – the count of documents you have indexed and how many storage you currently consume. Not that much to show here.

Query

The query side was more work, but it is definitely worth it. Currently there are 16 query parameters available (see specification) and the AzureSearchTool now assists you entering them. Some of the fields should be Url-Encoded so I handled that one, too.

The picture shows a rather basic query for the token “dsds”:

All options are handled now

All query options are handled now

That query results in a nice REST url that you can copy to your application:

https://MaxMelcher.search.windows.net/indexes/twittersearch/docs?api-version=2015-02-28-Preview&search=dsds&$top=7&$skip=1&$filter=Score%20gt%200.5&searchMode=any&searchFields=Text&$count=true&$orderby=Created&$select=Text,Mention&highlight=Text&highlightPreTag=%3Cli%3E&highlightPostTag=%3C%2Fli%3E

Create that by hand or with Postman? Rather not.

If you managed to enter invalid values in the search query parameters, the AzureSearchTool now shows the error that is returned by Azure Search:

That error is really helpful!

That error is really helpful!

Overall

I think the feature set almost doubled in this release. Next on I will work on Facets & Suggestions.

comments powered by Disqus