lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jack Krupansky" <>
Subject Re: What makes an Analyzer/Tokenizer/CharFilter/etc suitable for Solr?
Date Fri, 01 Mar 2013 04:04:47 GMT
The package Javadoc for Solr analysis is a good start:

Especially the AbstractAnalysisFactory:

Also, look at the various "factories" in solrconfig.xml for other Solr 
extension points.

Including search components, spellcheckers, etc.

-- Jack Krupansky

-----Original Message----- 
From: Alexandre Rafalovitch
Sent: Thursday, February 28, 2013 10:32 PM
Subject: What makes an Analyzer/Tokenizer/CharFilter/etc suitable for Solr?


I want to have a unified reference of all different processors one could
use in Solr in various extension points.

I have written a small tool to extract all implementations
of UpdateRequestProcessorFactory, Analyzer, CharFilterFactory, etc
(actually of any root class).

However, I assume not all Lucene Analyzer derivatives can be just plugged
into Solr.

Is it fair to say that the class must:
*) Derive from appropriate root (is there a list of ALL the roots?)
*) Be public and not abstract (though a common sub-root could be)
*) Have a default empty constructor

My preliminary tests seem to indicate this is the case. Am I missing

Personal blog:
- Time is the quality of nature that keeps events from happening all at
once. Lately, it doesn't seem to be working.  (Anonymous  - via GTD book) 

View raw message