: Therefore I turned back to the standard analyzer and now do some replacing
: of the underscores in my ID string to avoid my original problem. This solved
maybe i'm missing something, but if you've got a field in your doc that
represents an ID, why not create that field as "NonTokenized" so you d
On Dec 20, 2004, at 12:43 PM, Peter Posselt Vestergaard wrote:
Therefore I turned back to the standard analyzer and now do some
replacing
of the underscores in my ID string to avoid my original problem. This
solved
my phrase problem so that I can now search for phrases. However I
still have
the
Hi again
Thanks for your answer, Otis. My analyzer did not do anything else than
using the WhitespaceAnalyzer/LowerCaseFilter.
However I found out that I got problems with characters such as ",.:" when
searching because of my simple analyzer. (E.g. I would not be able to search
for "world" in the s
When searching for phrases, what's important is the position of each
token/word extracted by the Analyzer.
WhitespaceAnalyzer/LowerCaseFilter don't do anything with the
positional information. There is nothing else in your Analyzer?
In any case, the following should help you see what your Analyz
