Whether the configuration of content types in property 'caefeeder.content.type' includes subtypes. A change to this property will not trigger automatic re-indexing of formerly included or excluded content items. See the Search Manual, chapter "Reindexing" for details on re-indexing.

The paths of content items to feed. This property maps included base folder paths to the value 'true'. Paths start with a slash. Note, that the configuration of overlapping paths is not supported, and that entries with value 'false' are ignored. It is not possible to exclude a subfolder of an included folder. A change to this property will not trigger automatic re-indexing of formerly included or excluded content items. See the Search Manual, chapter "Reindexing" for details on re-indexing. This property is ignored, if deprecated property 'feeder.contentSelector.basePath' is still set.

The types of content items to feed. This property maps included content types to the value 'true'. Note, that entries with value 'false' are ignored and cannot be used to exclude a subtype of an included type. A change to this property will not trigger automatic re-indexing of formerly included or excluded content items. See the Search Manual, chapter "Reindexing" for details on re-indexing. This property is ignored, if deprecated property 'feeder.contentSelector.contentTypes' is still set.

The minimum delay between evaluations. Higher values lead to reduced throughput.

The delay between evaluations if the application is idle. Smaller values can be configured to reduce the latency but may lead to increased load on the database.

The time interval to log some statistics about the progress, including the number of keys that are currently invalid and still need to be computed. (Default unit is seconds)

The number of evaluate threads, which influences performance not only because evaluations can execute concurrently but also because higher values increase the probability that the CAE Feeder writes the state of multiple evaluations to the database in one database transaction.

Whether the CAE Feeder checks that the configured database and search engine index were initialized by the same CAE Feeder instance. If enabled, the CAE Feeder stores the same random token in both the database and the search engine index initially, and compares stored values when restarted.

Normally, this setting should not be changed. In case of problems or custom integrations of search engines that cannot store such a token, you can set this to false.

Whether dependency invalidation is paused. Invalidations will not be lost. They will be handled when invalidation is resumed.

The interval to invalidate timed dependencies, which represents the resolution of timed dependencies.

The maximum number of pending jobs to change stored dependencies. If the maximum is reached, scheduling more jobs for execution will fail.

Whether dependency names are stored as separate column in addition to dependency hashes in table pdcdependencies. This can be useful for debugging/monitoring but will decrease performance, increase the size of the table, and is not recommended for production usage.

The maximum weight of a database transaction to change stored dependencies. The weight is interpreted as the number of changed keys, that is, a transaction with one deleted key has weight 1. Multiple transactions will be used to process an event that causes the invalidation of more keys.

Whether the CAE Feeder should be reset, and database tables should be cleared on application startup. If true, previous data will be lost.

Whether dependency invalidation is paused.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.invalidation.paused instead.

Reason:

The property was renamed.

The maximum number of pending jobs to change stored dependencies.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.store.dependency-job-queue-capacity instead.

Reason:

The property was renamed.

The maximum weight of a database transaction to change stored dependencies.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.store.dependency-transaction-max-weight instead.

Reason:

The property was renamed.

Whether dependency names are stored as separate column in addition to dependency hashes in table pdcdependencies. This can be useful for debugging/monitoring but will decrease performance, increase the size of the table, and is not recommended for production usage.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.store.dependency-names instead.

Reason:

The property was renamed.

A comma-separated list of excluded MIME types for blob values added by the BeanMappingFeedablePopulator.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use feeder.blob.enabled instead.

Reason:

The property was replaced by 'feeder.blob.enabled', which takes a map value instead of a comma-separated list and also limits blobs that are added by custom FeedablePopulator implementations.

A comma-separated list of included MIME types for blob values added by the BeanMappingFeedablePopulator.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use feeder.blob.enabled instead.

Reason:

The property was replaced by 'feeder.blob.enabled', which takes a map value instead of a comma-separated list and also limits blobs that are added by custom FeedablePopulator implementations.

The maximum size in bytes for the value of a bean property or -1 for no limitation. Larger values are ignored and will not be sent to the Search Engine.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use feeder.blob.max-size[*/*] instead.

Reason:

The property was replaced by 'feeder.blob.max-size', which allows configuration by MIME-type and also limits blobs that are added by custom FeedablePopulator implementations.

The MIME-types of indexed blobs.

This property maps included MIME-types to true, and excluded MIME-types to false. Entries for more specific types like text/xml override mappings for less specific types like text/*.

Example Configuration:

 feeder.blob.enabled[application/pdf]=true 

If the map does not contain any enabled MIME-type, then the catch-all type */* is enabled implicitly.

See also property feeder.blob.max-size, which restricts blobs based on their size. Blobs are only included if allowed by both feeder.blob.enabled and feeder.blob.max-size.

The maximum size of indexed blobs per MIME-type. Larger blob values will be skipped.

This property maps MIME-types to their maximum size. Values must be non-negative. Entries for more specific types like text/xml override mappings for less specific types like text/*.

Example Configuration:

 feeder.blob.max-size[application/pdf]=5MB 

If the map does not contain a configuration for an enabled MIME-type, then blobs of that MIME-type are indexed regardless of their size.

See also property feeder.blob.enabled, which restricts blob values based on type. Blobs are only included if allowed by both feeder.blob.enabled and feeder.blob.max-size.

A comma-separated list of base folder paths below which content beans are indexed.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.content.path instead.

Reason:

The property was replaced by 'caefeeder.content.path', which takes a map value instead of a comma-separated list.

A comma-separated list of content types for which content beans are indexed.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.content.type instead.

Reason:

The property was replaced by 'caefeeder.content.type', which takes a map value instead of a comma-separated list.

Whether the configuration of content types includes subtypes.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.content.include-subtypes instead.

Reason:

The property was renamed.

Whether the CAE Feeder should be reset, and database tables should be cleared on application startup. If true, previous data will be lost.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.store.reset instead.

Reason:

The property was renamed.

The time interval in seconds to log some statistics about the progress, including the number of keys that are currently invalid and still need to be computed.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.evaluation.log-interval instead.

Reason:

The property was renamed.

The minimum delay in milliseconds between evaluations.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.evaluation.delay instead.

Reason:

The property was renamed.

The number of evaluate threads.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.evaluation.threads instead.

Reason:

The property was renamed.

The delay in milliseconds between evaluations if the application is idle.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.evaluation.idle-delay instead.

Reason:

The property was renamed.

The interval in milliseconds to invalidate timed dependencies, which represents the resolution of timed dependencies.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.invalidation.timed-dependency-interval instead.

Reason:

The property was renamed.

Login password of the database, possibly encrypted.

JDBC URL of the database connection for the CAE Feeder.

Login username of the database.

Fully qualified name of the JDBC driver (ignored).

This property has been deprecated since 2412.0.0 and will be removed in a future version.

Use caefeeder.datasource.driver-class-name instead.

Reason:

The database driver class name does not need to be specified anymore, because it gets auto-detected for the JDBC URL. If really needed, the auto-detected driver class name can still be overridden with property 'caefeeder.datasource.driver-class-name'.

Login username of the database.

This property has been deprecated since 2412.0.0 and will be removed in a future version.

Use caefeeder.datasource.username instead.

Reason:

The property was renamed to use the 'caefeeder.datasource' prefix, which exposes more data source properties from org.springframework.boot.autoconfigure.jdbc.DataSourceProperties. Use 'caefeeder.datasource.username' instead with the full login username.

Login password of the database, possibly encrypted.

This property has been deprecated since 2412.0.0 and will be removed in a future version.

Use caefeeder.datasource.password instead.

Reason:

The property was renamed to use the 'caefeeder.datasource' prefix, which exposes more data source properties from org.springframework.boot.autoconfigure.jdbc.DataSourceProperties.

JDBC URL of the database.

This property has been deprecated since 2412.0.0 and will be removed in a future version.

Use caefeeder.datasource.url instead.

Reason:

The property was renamed to use the 'caefeeder.datasource' prefix, which exposes more data source properties from org.springframework.boot.autoconfigure.jdbc.DataSourceProperties.

Login username of the database.

This property has been deprecated since 2412.0.0 and will be removed in a future version.

Use caefeeder.datasource.username instead.

Reason:

The property was renamed to use the 'caefeeder.datasource' prefix, which exposes more data source properties from org.springframework.boot.autoconfigure.jdbc.DataSourceProperties. Use 'caefeeder.datasource.username' instead with the full login username.

The application identifier that is used to identify the owning application of a lock stored in the database. If unset, the application identifier will be computed as [hostname]/[ip]:[current working directory]:[applicationName].

The application name that will be used to compute an application identifier, if not set with 'caefeeder.lock.application-identifier'.

The minimum time to wait between checking the database if a requested lock has been unlocked.

Whether locking is enabled.

The time after which a lock is considered expired, if not refreshed.

The time between refreshing acquired locks in the database.

The time to wait for a lock to become available, or 0 to not wait.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.lock.enabled instead.

Reason:

The property was renamed.

This property has been deprecated since 2506.0.0 and will be removed in a future version.

Use caefeeder.lock.timeout instead.

Reason:

The property was renamed.

Comma-separated list of metadata identifiers returned by Apache Tika to append to the extracted body text.

The location of a custom Tika Config XML, for example to customize the default Tika parsers. See Apache Tika documentation for details on configuring Tika. The value of this property must be a Spring Resource location (e.g. file:/path/to/local/file) or empty for defaults.

Comma-separated list of metadata identifiers returned by Apache Tika and names of Feedable elements to copy the metadata to. Entries in the comma separated list have the following format: "metadata identifier"="element name".

With Apache Solr, target index fields must be defined as multiValued="true" to avoid indexing errors if there are multiple metadata values with the same identifier.

The MIME-types of blobs in Feedable elements to parse with Apache Tika for plain text and/or metadata extraction.

This property maps included MIME-types to true, and excluded MIME-types to false. Entries for more specific types like application/pdf override entries for less specific types like application/*. If the property does not map any MIME-type to true, then the catch-all type */* is included implicitly.

Blobs of included MIME-types are parsed with Apache Tika, and are replaced with their extracted plain text and optional metadata in Feedable elements, so that the indexer receives string values.

Blobs of excluded MIME-types are not parsed with Apache Tika, and are kept unchanged in Feedable elements, so that the indexer receives the original binary data.

See also related property feeder.blob.enabled, which generally restricts feeding of blobs by MIME-type. Blobs that have been excluded with that property are neither parsed with Apache Tika, nor passed as binary data to the indexer.

Example configuration: Parse all blobs except JPEG images

 feeder.tika.parse[image/jpeg]=false 

Note, that MIME-type */* is included implicitly in this example, because no type is explicitly mapped to true.

The maximum time after which text extraction from binary data with Apache Tika fails. If extraction fails, the binary data will be skipped for the index document. Lower values will avoid that the Feeder is blocked for a long time in text extraction.

The time after which a warning is logged when text extraction from binary data with Apache Tika takes some time.

Sets whether Apache Tika's "Zip bomb" prevention is enabled. When a "Zip bomb" is detected, no text will be extracted from the Blob, but a warning will be logged. Note that "Zip bombs" are not restricted to ZIP files but also apply to PDFs or other formats. Disabled "Zip bomb" prevention bears the risk of OutOfMemoryError-s. Note that false positives are possible.

Sets the ratio between output characters and input bytes for the Apache Tika "Zip bomb" prevention. If this ratio is exceeded (after the output threshold has been reached) then no text will be extracted and a warning will be logged. Set to -1 to use the default of Apache Tika.

Sets the maximum XML element nesting level for the Apache Tika "Zip bomb" prevention. If this depth level is exceeded then no text will be extracted, and a warning will be logged. Set to -1 to use the default of Apache Tika.

Sets the maximum package entry nesting level for the Apache Tika "Zip bomb" prevention. If this depth level is exceeded then no text will be extracted, and a warning will be logged. Set to -1 to use the default of Apache Tika.

Whether storing nested feedables as nested documents is supported in Solr. This requires that the Solr schema contains a _root_ field. Note that if you add that field to the schema, you have to recreate the index from scratch.

If feeder.solr.nested-documents.enabled is true, the Solr index schema is checked whether it contains the _root_ field. The Feeder will log a warning and not use nested documents, if feeding of nested documents is attempted but the index does not support it. You can set this property to true to skip checking the index schema.

The delay to wait before the Feeder retries to send data after failures from Solr.

The name of the Solr collection for web-site search. This property is typically set to 'preview' or 'live' depending on the environment.

The name of the Solr config set to use when creating the CAE collection. This property is used by the CAE Feeder.

Whether to connect to SolrCloud. If true, connect to a SolrCloud cluster. SolrCloud connection details must be set either as ZooKeeper addresses (solr.zookeeper.addresses) or, if the former is unset or empty as HTTP URLs (solr.url). If false, connect to stand-alone Solr nodes via HTTP URLs (solr.url).

The connection timeout set on the SolrJ SolrClient. It determines how long the client waits to establish a connection without any response from the server.

The default value 0 means, that it will wait forever. Set a negative value to use the SolrClient default. (Default unit is milliseconds)

Value for the "dataDir" parameter of the Solr CoreAdmin API / Collection API request to create a Solr index.

Password for HTTP basic authentication, used if a non-empty solr.username has been specified. The value may have been encrypted with the tool "cm encryptpasswordproperty".

Proxy host for Solr communication that needs to be set if a proxy should be used.

Secure flag for Solr proxy.

SOCKS 4 flag for Solr proxy.

Proxy port for Solr communication that needs to be set if a proxy should be used.

The socket timeout set on the SolrJ SolrClient. It determines how long the client waits for a response from the server after the connection was established and the request was already sent.

Set to 0 for no timeout, or to a negative value to use SolrClient default. (Default unit is milliseconds)

The list of Solr URLs to connect to. These URLs are ignored if connecting to SolrCloud (solr.cloud=true) and non-empty ZooKeeper addresses (solr.zookeeper.addresses) have been set. For a Feeder application that is not connected to a SolrCloud cluster, a single URL to the Solr leader must be configured.

Whether HTTP/1 (true) or HTTP/2 (false) shall be used by Solr clients.

This property has been deprecated and will be removed in a future version.

Whether SolrJ should use XML response format instead of Javabin format.

Username for HTTP basic authentication, or empty string for no authentication.

ZooKeeper addresses for connecting to SolrCloud. Only used if solr.cloud=true.

Optional ZooKeeper chroot path for Solr. ZooKeeper chroot support makes it possible to isolate the SolrCloud tree in a ZooKeeper instance that is Only used if solr.cloud=true and solr.zookeeper.addresses is set to non-empty value.

Client-timeout duration for ZooKeeper. Set to a negative value to use SolrClient default. (Default unit is milliseconds)

Only used if solr.cloud=true and solr.zookeeper.addresses is set to non-empty value.

Connect-timeout duration for ZooKeeper. Set to a negative value to use SolrClient default. (Default unit is milliseconds)

Only used if solr.cloud=true and solr.zookeeper.addresses is set to non-empty value.

The maximum batch size in bytes. The Feeder sends a batch to the search engine if its maximum size would be exceeded when adding more entries. Note, that byte computation is a rough estimate only. A smaller batch may be sent if the maximum number of index documents is reached before, or if configured delays are reached.

The Content Feeder default value is 5 MB.

The CAE Feeder default value is 20 MB.

The maximum number of batches indexed in parallel. This setting is not used with the default integration of Apache Solr but only with custom implementations of the com.coremedia.cap.feeder.index.async.AsyncIndexer interface. The Feeder does not call the index method of the AsyncIndexer interface to index another batch if the maximum number of parallel batches has been reached. The method will not be called until a callback about the persistence of one of these batches has been received.

The maximum number of batches processed by the Indexer in parallel. This setting is not used with the default integration of Apache Solr but only with custom implementations of the com.coremedia.cap.feeder.index.async.AsyncIndexer interface. The Feeder does not call the index method of the AsyncIndexer interface to index another batch if the configured number of currently processed batches has been reached. The method will not be called until a callback about completed processing or persistence of one of these batches has been received.

The maximum number of index documents in a batch. If the maximum number is reached, the Feeder sends the batch to the search engine. A smaller batch may be sent if the maximum byte size is reached before, or if configured delays are reached.

The time to wait before retrying to send index documents to the search engine after failures. This delay is used if the feeder is idle.

The maximum time to wait before retrying to send index documents to the search engine after failures. This delay is used if the feeder is not idle. The setting is typically larger than retry-send-idle-delay.

The time between adding an index document to a batch and sending that batch to the search engine, if the batch is not yet full according to the max-size and max-bytes configuration properties, and if the feeder is idle. If a change needs to be sent to the search engine, and no further changes were made within the specified time, then an index document for the change will be sent after that time to the search engine. A small delay ensures low latency for changes to become visible in the search engine, as long as the system is not too busy.

The Content Feeder default value is 3 seconds.

The CAE Feeder default value is 10 seconds.

The maximum time between adding an index document to a batch and sending that batch to the search engine. This setting is typically larger than send-idle-delay to allow batches to grow and increase throughput, for example when large amounts of content are created by an import process. The configured value may still be exceeded under high load, or if there are problems connecting to the search engine.

The Content Feeder default value is 20 seconds.

The CAE Feeder default value is 2 minutes.

Maximum capacity of the Feeder's executor queue, which is internally used to transfer evaluated values.

The Content Feeder default value is 100.

The CAE Feeder default value is 2000.

The delay to wait before the Feeder retries to access the source data after failures.