The directory that contains the locks for lucene indexes.
Transformations of content that are likely to take longer than this time (in millis) will be done in the background. To force atomic content indexing, increase this value.
Max Clauses (Lucene standard parameter)
Lucene queries limit the number of clauses in a boolean query to this value. Some queries are expanded into a whole set of boolean query with many clauses under the covers. For example, searching for luc* will expand to a boolean query containing an 'OR' for every token the index knows about that matches luc*.
Batch size (Alfresco indexing parameter)
The indexer stores a list of what it has to do as changes are made using the node service API. Typically, there are many events that would cause a node to be re-indexed. Keeping an event list means the actions can be optimized - the algorithm limits re-indexes to one per batch size, and will not index if a delete is pending, etc. When the list of events reaches this size, the whole event list is processed and documents are added to the delta index.
Set high to workaround http://issues.alfresco.com/browse/AR-1280
Could be set lower for an index rebuild
Caching is carried across an index, for the composite index reader.
Enable/disable index level caching
Cache index doc id to NodeRef.
This cache is designed to avoid a disk read and synchronization when finding the noderef association with a lucene document
Lucene currently sychronises on reading a document.
Cache for lucene documents by lucene index doc id
Cache which lucene docs are Alfresco categories (-1 caches all)
Cache link aspects (increase to improve the performance of category queries)
Used in linking children to aspects
Cache parent lookups (increase to improve the performance of PATH queries)
Used in linking children to parents
CATEGORY and PATH
Cache the first part of category PATH lookups
Cache alfresco type for docs in the lucene index
Options specific to IndexWriters used in background merging. These options only apply to the merge process - the resulting index will be optimised.
Options specific to IndexWriters used for transactional indexes. These optoins only apply to the index process - the resulting index will be optimised.
Options to control merging behaviour
Target for the number of indexes (more than this an we start merging)
Target for the number of indexes that relate directly to a transaction.
More thhe this and we start merging deletions an trnsformning overlays to indexes.
The indexing behavior of each property can be set in the content model. By default, they are indexed atomically. The property value is not stored in the index, and the property is tokenized when it is indexed.
The following example shows how indexing can be controlled.
If this is false, there will be no entry for this property in the index.
If this is true, the property is indexed in the transaction if not the property is indexed in the background.
Indexing of content that requires transformation before being indexed (e.g. PDFs) will only obey Atomic=true if the transformation takes less time than the value specified for lucene.maxAtomicTransformationTime. See #General.
If true, the property value is stored in the index and may be obtained via the Lucene low-level query API.
This can be useful while debugging systems to see exactly what is being indexed, but do not set this to true on production systems.
If 'true', the string value of the property is tokenized before indexing
if 'false', it is indexed 'as is' as a single string
if 'both' then both forms above are in the index
All content is not stored, indexed, and tokenized, if it is indexed.
The tokenizer is determined by the property type in the data dictionary. This is locale sensitive as supported by the data dictionary â€” so you could switch to tokenize all your content in German. At the moment you cannot mix German and English tokenization.