Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
<sitecore>
<contentSearch>
<indexConfigurations>
<!-- If no configuration is specified for an index, it uses the default configuration. The configurations are not merged if the index also has a
configuration. The system uses either the default configuration or the index configuration. -->
<yourCustomLuceneIndexConfiguration type="Sitecore.ContentSearch.LuceneProvider.LuceneIndexConfiguration, Sitecore.ContentSearch.LuceneProvider">
<!-- Should index Initialize() method be called as soon as the index is added or wait for an external trigger -->
<initializeOnAdd>true</initializeOnAdd>
<!-- DEFAULT ANALYZER FOR ALL FIELDS
This is the default analyzer used by all fields to index and query with. The StandardAnalyzer is by far the most versatile
and powerful of all of the Analyzers.
The StandardAnalyzer is quite time consuming. You may need to experiment with Analyzers to find the one that suits you best.
-->
<analyzer ref="contentSearch/indexConfigurations/defaultLuceneIndexConfiguration/analyzer" />
<!-- DEFAULT FIELD MAPPING
The field map allows you to have full control over the way your data is stored in the index. This affects the way data is queried,
the performance of searching, and the way that data is retrieved and cast to a proper type in the API.
-->
<fieldMap ref="contentSearch/indexConfigurations/defaultLuceneIndexConfiguration/fieldMap" />
<!-- VIRTUAL FIELDS
Virtual fields can be used to translate a field query into a different query.
-->
<virtualFields ref="contentSearch/indexConfigurations/defaultLuceneIndexConfiguration/virtualFields" />
<documentOptions ref="contentSearch/indexConfigurations/defaultLuceneIndexConfiguration/documentOptions" />
<!-- MEDIA ITEM CONTENT EXTRACTOR FILE MAPPING
This map allows you to specify the extensions and mimetypes that we will pass through to the IFilters on your machine so they can be indexed.
We also allow you to include all files or exclude all files and leave it to the IFilters to control what is and is not indexed.
-->
<mediaIndexing ref="contentSearch/indexConfigurations/defaultLuceneIndexConfiguration/mediaIndexing" />
<!-- FIELD READER MAP
This setting maps a field type by name to a strongly typed implementation of the field type. For example, 'html' maps to the 'RichTextFieldReader' class.
-->
<fieldReaders ref="contentSearch/indexConfigurations/defaultLuceneIndexConfiguration/fieldReaders" />
<!-- INDEX FIELD STORAGE MAPPER
Maintains a collection of all the possible Convertors for the provider.
-->
<indexFieldStorageValueFormatter ref="contentSearch/indexConfigurations/defaultLuceneIndexConfiguration/indexFieldStorageValueFormatter" />
<!-- INDEX DOCUMENT TO PROPERTY MAPPER
Maintains a collection of all the possible Convertors for the provider.
-->
<indexDocumentPropertyMapper ref="contentSearch/indexConfigurations/defaultLuceneIndexConfiguration/indexDocumentPropertyMapper" />
<!-- DOCUMENT BUILDER
Allows you to override the document builder. The document builder class processes all the fields in the Sitecore items and prepares
the data for storage in the index.
You can override the document builder to modify how the data is prepared, and to apply any additional logic that you may require.
-->
<documentBuilderType>Sitecore.ContentSearch.LuceneProvider.LuceneDocumentBuilder, Sitecore.ContentSearch.LuceneProvider</documentBuilderType>
<defaultSearchSecurityOption ref="contentSearch/indexConfigurations/defaultSearchSecurityOption" />
</yourCustomLuceneIndexConfiguration>
</indexConfigurations>
</contentSearch>
</sitecore>
</configuration>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.