Alternatively, it may be horribly complex and messy if the content is scattered in all sorts of places (file systems, content management systems, Microsoft Exchange, Lotus Domino, various websites, databases, local XML files, CGI scripts running on intranet servers, and so forth). ![]() That may be trivial, for example, if you’re indexing a set of XML files that resides in a specific directory in the file system or if all your content resides in a wellorganized database. ![]() This process, which involves using a crawler or spider, gathers and scopes the content that needs to be indexed. The first step, at the bottom of the above figure, is to acquire content. In the figure above, only the shaded components show are handled by Lucene. A common misconception is that Lucene is an entire search application, when in fact it’s simply the core indexing and searching component. If you would like to add one let me know in the comments or on Twitter.It’s important to grasp the big picture so that you have a clear understanding of which parts Lucene can handle and which parts your application must separately handle. I am sure I missed lots of great resources for learning Lucene. I hope there is something useful for you in this post. One example for Elasticsearch: If you would like to learn about how the common multi_match-Query is implemented in Lucene you will easily find the class MultiMatchQuery that creates the Lucene queries. Of course you need to find your way around the sources of the project but sometimes this isn’t too hard. Sourcesįinally, the project is open source so you can learn a lot about it by reading the source code of either the library or the tests.Īnother option is to look at applications using it, either Solr and Elasticsearch. You can find lots of video recordings of the past events on their website. Lucene is a regular topic on two larger conferences: Lucene/Solr Revolution and Berlin Buzzwords. There are also some interesting posts on the Lucidworks Blog and I am sure there are lots of other blogs I forgot to mention here. There is a lot of content about Lucene on the elastic Blog, if you want to hear about current development I can recommend the “This week in Elasticsearch and Apache Lucene” series. Some blogs publish regular pieces on Lucene, recommended ones are by Mike McCandless (who now mostly blogs on the elastic Blog), OpenSource Connections, Flax and Uwe Schindler. There are countless blog posts on Lucene, a very good introduction is Lucene: The Good Parts by Andrew Montalenti. (If you can read German I am of course inviting you to read my book on Elasticsearch.) Blogs, Conferences and Videos I can recommend Elasticsearch in Action, Solr in Action and Elasticsearch – The definitive Guide. You can also learn a lot about different aspects of Lucene by reading a book on one of the search servers based on it. (I am making lots of grammar mistakes myself when blogging – but I am expecting more from a published book.) Additionally it felt to me as if no editor worked on this book, there are lots of repetitions, typos and broken sentences. ![]() It contains more current examples but is not suited well for learning the basics. Still it’s the recommended piece on learning Lucene.Īnonther book I’ve read is Lucene 4 Cookbook published at Packt. Also the newer concepts are not included. Unfortunately some of the information is outdated and lots of the code examples won’t work anymore. On over 500 pages it explains all the underlying concepts in detail. The classic book about the topic is Lucene in Action. It also contains a searchable version of the Javadocs. Though dedicated to Solr the list of analyzer components can be useful to determine analyzers for Lucene as well. When looking at analyzer components the Solr Start website can be useful.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |