*Warm Regards,*
*Amitesh K*
---------- Forwarded message ---------
From: Amitesh Kumar <amitesh116@gmail.com>
Date: Wed, Jul 12, 2023 at 7:03?AM
Subject: How to retain % sign against numbers in lucene indexing/ search
To: <dev@lucene.apache.org>
Hi Group,
I am facing a requirement change to get % sign retained in searches. e.g
Sample search docs:
1. Number of boys 50
2. My score was 50%
3. 40-50% for pass score
Search query: 50%
Expected results: Doc-2, Doc-3 i.e.
My score was 50%
40-50% for pass score
Actual result: All 4 documents
On the implementation front, I am using a set of filters like
lowerCaseFilter, EnglishPossessiveFilter etc in addition to base tokenizer
StandardTokenizer.
My analysis suggests, StandardTOkenizer strips off the % sign and hence
the behavior.Has someone faced similar requirements? Any help/guidance is
highly appreciated.
*Warm Regards,*
*Amitesh K*
*Amitesh K*
---------- Forwarded message ---------
From: Amitesh Kumar <amitesh116@gmail.com>
Date: Wed, Jul 12, 2023 at 7:03?AM
Subject: How to retain % sign against numbers in lucene indexing/ search
To: <dev@lucene.apache.org>
Hi Group,
I am facing a requirement change to get % sign retained in searches. e.g
Sample search docs:
1. Number of boys 50
2. My score was 50%
3. 40-50% for pass score
Search query: 50%
Expected results: Doc-2, Doc-3 i.e.
My score was 50%
40-50% for pass score
Actual result: All 4 documents
On the implementation front, I am using a set of filters like
lowerCaseFilter, EnglishPossessiveFilter etc in addition to base tokenizer
StandardTokenizer.
My analysis suggests, StandardTOkenizer strips off the % sign and hence
the behavior.Has someone faced similar requirements? Any help/guidance is
highly appreciated.
*Warm Regards,*
*Amitesh K*