Somehow we're mis-communicating here. Forget expansion,
it's all about base forms. .
bq: What I cannot figure out is how is this going to help me in instructing
Solr to execute the query for the different grammatical variations of the
input search term stem
You don't. You search the stemmed input
I was just wondering if another solution might work. If we are able to extract
the stem of the input search term(maybe using a C# based stemmer, some open
source implementation of the Porter algorithm) for cases where the stemming
option is selected, and submit the query to solr as a multiple ch
So the general solution is to index the field twice, once with stemming and
once without in order to have the ability to do both stemmed and exact matches
I am already indexing the text twice using the ContentSearch and
ContentSearchStemming fields. But what this allows me is to return "burnin
bq: But looks like it is executing the search for an exact text based
match with the stem "burn".
Right. You need to appreciate index time as opposed to query time stemming.
Your field
definition has both turned on. The admin/analysis page will help here ..
At index time, the terms are stemmed,
Hi Erick,
Thanks for the reply.
Here is what the situation is:
Relevant portion of Solr Schema:
First, this is for the Java version, I hope it extends to C#.
But in your configuration, when you're indexing the stemmer
should be storing the reduced form in the index. Then, when
searching, the search should be against the reduced term.
To check this, try
1> Using the Admin/Analysis page to see