IBM FileNet P8, Version 5.2.1            

Index partitions and index area capacity

Index partitions cause Content Platform Engine to create more full-text indexes than would otherwise be the case. This high number of potential indexes affects the index area capacity that you want to configure. Also, the configured index area capacity partly determines the number of full-text indexes that are created.

One or more full-text indexes are created for each set of objects with the same partition property values. For example, suppose that some objects have email as the string partition property value and January 1, 2010 as the date partition property value. Originally, this set of objects is indexed to one full-text index. If the resource status of the original index changes, however, another index might be created for this set of objects as new objects are indexed. The status of the original index might change for the following reasons:

Some objects can have no value for a partition property in the following sense: the objects belong to a class that does not have the property. For these objects, Content Platform Engine creates separate full-text indexes as if no value were a distinct property value.

You set the maximum number of full-text indexes for an index area with the Maximum index count property in the administration console. Set this maximum to be at least one greater than the anticipated number of index partitions. (For each index area, a separate index can be created for each index partition.) For example, if the anticipated number of index partitions is 10, you set the maximum number of indexes per index area to 11 or higher. As indicated in the following examples, the anticipated number of index partitions is based on the expected number of distinct partition property values:
Example Anticipated index partitions
  • You configured one partition property for the object store.
  • In your indexed documents, you expect 10 distinct values for the partition property.
10
  • You configured two partition properties for the object store.
  • In your indexed documents, you expect 11 distinct values for the first partition property.
  • In your indexed documents, you expect 12 distinct values for the second partition property.
132 (because 11 distinct values for the first property times 12 distinct values for the second property equals 132)


Last updated: March 2016
p8pcc214.htm

© Copyright IBM Corporation 2016.