Beckshome.com: Thomas Beck's Blog

The code and code narrative below reflects the changes that have been made on top of the first 4 posts. All source code is available online for this highlighting post.

In this third installment of my Blazor + Lucene.Net series, I’ll start tackling some advanced Lucene functionality, namely auto-complete. For advanced Lucene work, the most important lessons is don’t roll your own functionality. If you go to the docs for the Lucene.Net API, you’ll see that a ton of additional functionality is built into Lucene via modules. Modules exist for faceting, highlighting, spatial search and autosuggest, amongst others. Lots of the examples and StackOverflow answers are roll-your-own solutions – don’t do it!!

In the first installment of this series, we looked at returning results from a limited pool of items in a Lucene full text index. In this second installment, we significantly increase the number of generated items (3,000, by default) and add a numbered paging system, as used by the main commercial search engines and search sites.

The code and code narrative below reflects the changes that have been made since the first post. All source code is available online for this results paging post.

While useful and recent tutorials exist on using Lucene.NET in a command line context, there is a dearth of tutorials on using Lucene.NET in a web context, especially with the current Blazor framework. This tutorial fills that gap, with this existing article being the first in a series that will illustrate the buildout of a Blazor-based search site.