Use custom JAR files with Search
Search supports custom plug-in code. You load classes into JAR files and then configure Search to find these files.
To correctly deploy custom JARs, ensure that:
- Custom JARs are pushed to the same location on all hosts in your cluster that are hosting Cloudera Search (Solr Service).
- Supporting configuration files direct Cloudera Search to find the custom JAR files.
- Any required configuration files such as
schema.xml
orsolrconfig.xml
reference the custom JAR code.
The following procedure describes how to use custom JARs. Some cases
may not require completion of every step. For example, indexer tools
that support passing JARs as arguments may not require modifying
xml
files. However, completing all configuration
steps helps ensure the custom JARs are used correctly in all cases.
The system is now configured to find custom JAR files. Some command-line
tools included with Cloudera Search support specifying JAR files. For
example, when using
MapReduceIndexerTool
, use the
--libjars
option to specify JAR files to use. Tools
that support specifying custom JARs include:- MapReduceIndexerTool
- Lily HBase Indexer
- CrunchIndexerTool