The Luke artifact of the Lucene development sequence

Lucene is a very good full-text retrieval of open Source Library, the latest version is lucene4.4, about Lucene's historical background and development situation, here I do not introduce, if you really wish to learn lucene, presumably before you have done some understanding of this.

There are a lot of people who know Lucene or SOLR, but there are very few people who know Luke, and here is a brief introduction to Luke, a third-party tool for Lucene search engines that facilitates development and diagnostics, which can access existing Lucene indexes, and allows you to display and modify and debug. Luke is the first Google offer, for Lucene Direct index view is very convenient, before this, if you want to see the index of the lucene you generated all the content, you need to write a lot of code to operate, more, perhaps you just want to simply look at the total amount of data generated index, You also have to write a piece of code to be counted, and Luke's appearance, for Lucene view and debugging, provides a good interface operation tool, the index generated by Lucene and SOLR can be very convenient query and debugging, not only so Luke also provides a good plug-in mechanism, Users can customize some features for installation and use, very flexible.

Using the Luke tool, you can not only view the index directly, but also add, delete, modify, and optimize the index, or use a different word breaker, word-breaker for a particular field, and so on, which is very similar to the functionality provided by the SOLR Administration page, but the focus is not one place.

The use of Luke Tools is also very simple, after downloading Luke directly placed under a drive letter and can be found in the cmd window of the descriptor path of the Luke tool, using Java-jar Luke.jar can start, some of Luke tools directly double-click Run can start, use time two ways can try, after launch, click the browser button, find your index path point OK, you can display the content of your index, but use Luke to pay attention to the version problem, In general, Luke is backwards compatible, but if you are a 4.x Lucene index, then you use the 3.x Luke tool to view it, which is not possible, but it does.

Luke Installation and use

1, first configure the Java environment.

2, download Luke:http://www.getopt.org/luke/luke-0.9.2/lukeall-0.9.2.jar.

3, double-click Lukeall-0.9.2.jar.

4. Select the index file to view.

In addition, Luke's plugin with an analyzer test tool.

By selecting the plugins tag in Luke and selecting the Analyzer tool, you will be able to use this Instrument for testing analyzer. Select the analyzer you want to test in the drop-down list, then enter the text you want to analyze, and then click Analyze to see the token that you analyzed. This tool can test a lot of analyzer, in addition to the most basic Whitespaceanalyzer, Stopanalyzer, Simpleanalyzer, StandardAnalyzer can also experiment Keywordanalyzer , Snowballanalyzer, Cjkanalyzer, Chineseanalyzer and so on, can be said to be all-encompassing.

Before writing the index and searching the program, you can use this tool to compare the results of the various analyzer runs. It is also possible to test your analyzer class if you write your own analyzer and add it to the corresponding location in Luke's jar package.

: http://download.csdn.net/detail/irfen/7700397#comment

After downloading, you can simply double click

The Luke artifact of the Lucene development sequence