The default serializer is a simple one that handles top-level fields, but does not render collections or nested objects. The index has an associated serializer that renders the indexed object as a Lucene document comprised of searchable fields. When no analyzer is specified, the .standard.StandardAnalyzer is used. _REGION_VALUE_FIELD serves as the field name for entry values of all primitive types, including String, Long, Integer, Float, and Double.Įach field has a corresponding analyzer to extract terms from text. If the object value for the entries in the region comprises a primitive type value without a field name, then use _REGION_VALUE_FIELD to specify the field to be indexed. You must specify at least one field to be indexed. The names of the fields you wish to index.The name of the region to be indexed and searched.The name of the index you wish to create.When you create a Lucene index, you must provide three pieces of information: Note: Create the Lucene index before creating the region.

Heterogeneous objects in a single region are supported.Multiple indexes can be defined for a single region. A Lucene index applies to only one region.You cannot create a Lucene index on a client. Replicated region types are not supported. Apache Lucene indexes are supported only on partitioned regions.You can interact with Apache Lucene indexes through a Java API, through the gfsh command-line utility, or by means of the cache.xml configuration file. Provides scalability by partitioning index dataįor more details, see Javadocs for the classes and interfaces that implement Apache Lucene indexes and searches, including LuceneService, LuceneSerializer, LuceneIndexFactory, LuceneQuery, LuceneQueryFactory, LuceneQueryProvider, and LuceneResultStruct.Updates the indexes asynchronously to minimize impacting write latency.For persistent regions, persists Lucene indexes to disk.Provides high availability of indexes using GemFire’s HA capabilities to store the indexes in memory.Enables users to create Lucene indexes on data stored in GemFire.We assume that the reader is familiar with Apache Lucene’s indexing and search functionalities. This section describes how VMware GemFire integrates with Apache Lucene. But if you want to change this configuration property after the OpenKM repository has been created you need to rebuild the Lucene indexes.Apache Lucene® is a widely used Java full-text search engine. If you configure the search analyzer before the first time you start OpenKM, the Lucene indexed will be created using this analyzer.

You can see all the available analyzer in the here, here and here. If you are working with oriental languages like Chinese or Japanese you have several analyzers to use. This can be done editing the OpenKM.cfg file and setting the configuration property.īy default, OpenKM use the .standard.StandardAnalyzer which works fine with english and most languages, but you can get better search results configuring more specific analyzer for you language. OpenKM 6.0 has more flexible indexing configuration, based in Apache Lucene.įor example, depending on the lenguage used in the documents and properties, you have obtain better search results configuring a proper Lucene Analyzer. This feature is only available since OpenKM 6.0

Apache lucene configuration