Thank you Walter Under Underwood for a complete honest review.
I will start simple by using the sample.
Regards,LavanyaOn Tuesday, 22 January 2019, 12:31:55 pm AEDT, Walter
Underwood wrote:
There are many, many problems with this analyzer chain definition.
This is a summary of the i
There are many, many problems with this analyzer chain definition.
This is a summary of the indexing chain:
* WhitespaceTokenizerFilter
* LowerCaseFilter
* SynonymFilter (with ignoreCase=true after lower-casing everything)
* StopFilter (we should have stopped using stopwords 20 years ago)
* WordD
Thank you Aman Deep
I tried removing the kstem filter factory and still get the same issue, but
when i comment the Porterstemfilterfactory the character y does not get
replaced.
On Monday, 21 January 2019, 11:16:23 pm AEDT, Aman deep singh
wrote:
Hi Lavanya,
This is probably due t
thank you Mikhail. On Monday, 21 January 2019, 11:13:51 pm AEDT, Mikhail
Khludnev wrote:
querystring is what goes into QPaser, parsedquery is
LuceneQuery.toString()
On Mon, Jan 21, 2019 at 3:04 PM Lavanya Thirumalaisami
wrote:
> Hi,
> Our solr search is not returning expected resu
Hi Lavanya,
This is probably due to the kstem Filter factory it is removing the y charactor
,since the stemmer has rule of words ending with y .
Regards,
Aman Deep Singh
> On 21-Jan-2019, at 5:43 PM, Mikhail Khludnev wrote:
>
> querystring is what goes into QPaser, parsedquery is
> LuceneQ
querystring is what goes into QPaser, parsedquery is
LuceneQuery.toString()
On Mon, Jan 21, 2019 at 3:04 PM Lavanya Thirumalaisami
wrote:
> Hi,
> Our solr search is not returning expected results for keywords ending with
> the character 'y'.
> For example keywords like battery, way, accessory
Hi,
Our solr search is not returning expected results for keywords ending with the
character 'y'.
For example keywords like battery, way, accessory etc.
I tried debugging the solr query in solr admin console and i find there is a
difference between query string and parsed query.
"querystring":
