I previously wrote a blog post called Index data without writing code and recently received some interesting comments / questions in regards to using the Collection(Edm.String) collection datatype when having a SQL Server based data source. And I therefore decided to compile the information within a separate blog post. (Special thanks to the Azure search team for answering some of my queries!)
In this post, I want to cover Azure Search from a different perspective and share some details that might help people getting starting in the exciting world of search. The main focus will be on pointing out the underlying technology, helping you to understand better and build search solutions.
The Microsoft Azure Search team recently released a new preview version, which includes some exciting new features. I’ve briefly covered them in my previous Azure Search Services post but wanted to dive a bit deeper into the Indexers.
An indexer is a content crawler written for a specific data source eliminating the need for writing code responsible for extract data from your data source and feed this data within the index. The Indexer runs within the Azure context, and it’s therefore not required to create a service for hosting this process (billing details are not available yet).
Recent Comments