Examining indexes

If you want to check the contents of the index you can do this using a tool named Luke which you can download from this page.

Note: When you are done with Luke it is important to close the index to get Luke to release its lock on the index files.

Using Luke, you can open up your index and see its content. It should give you statistics on the elements, number of documents indexed, etc. Luke can also be used to run raw Lucene searches against your index. This can be helpful during development or to debug your queries.

Note: When you are done with Luke it is important to close the index to getLuke to release its lock on the index files.

Examining with Luke

When you open Luke you will be asked to insert the path of the index directory. By default Ucommerce places the indexes in the Ucommerce folder underneath the App_Data folder, an example is: ~/App_Data/Ucommerce/Indexes. If the path does not exist or it is empty, you will have to run a scratch index.

Ucommerce is using A/B switching, if you are interested you can read about it here. To point to the active index look at the active index file called A.active or B.active, this indicates the active index, point Luke to the active index with the culture you want, ex: ~/B\Product\ProductsIndexDefinition\244750fd\en-GB\index.

Debugging the queries

In your log files, you will be able to find verbose logging of the queries output via the APIs to Lucene. To help you understand what they mean, you can watch the following video below where a log entry will be dissected.