See Also
You are here: Full-Text Indexing > Lucene integration overview
ContentsIndexHome
PreviousUpNext
Lucene integration overview
Lucene integration overview

 

ScimoreDB encapsulates CLucene search engine, which is C++ port of Java Lucene text search engine API. For more information on CLucene go to: http://clucene.sourceforge.net/index.php/Main_Page

 

ScimoreDB has built-in SQL commands for querying and modifying Lucene full-text index. Current integration of full-text does not allow modifying Lucene index content directly, instead of Lucene index must be linked with DB table that will send all modifications as a single batch once transaction has been committed. Therefore, there can be a delay before full-text index reflects changes. The delay time depends of the amount of the changes made in DB table. For example: if SQL transaction updates 10 rows of single table, after commit, the Lucene index will receive a command batch of 10 deletes followed by 10 inserts, this will take less than a millisecond. If update batch is bigger, the Lucene indexing takes more time respectively. There are no limitations how many rows can be updated, since the batch for Lucene full-text index uses DB page pool for storage and cannot run out memory. 

 

In order to perform full-text indexing you need:

  1. Create full-text index
  2. Link index with DB table