Well, I'm not the greatest expert, but a quick look doesn't show me anything
obvious. But I have to ask, wouldn't WhiteSpaceAnalyzer work for you?
Although I don't remember whether WhiteSpaceAnalyzer lowercases or not.
It sure looks like you're getting reasonable results given how you're
tokenizi
I was browsing the sort javadocs and ran into this:
This class is not set up to be able to efficiently sort hits from more
than one index simultaneously.
Does this mean sorting with a muiltsearcher is very slow? Anyone have
any experience?
- mark
---
Hi Erick
Thanks for your response. There's a lot to chew on in your reply and Im
looking at the suggestions you've made.
Yeah I have Luke installed and have queried my index but there isn't any
great explanation Im getting out of it. A query for "6/12" is sent as
"TERM:6/12" which is quite
Most often, from what I've seen on this e-mail list, unexpected results are
because you're not indexing on the tokens you *think* you're indexing. Or
not searching on them. By that I mean that the analyzers you're using are
behaving in ways you don't expect.
That said, I think you're getting exac
Hi
I have a custom-built Analyzer where I tokenize all non-whitespace
characters as well available in the field "TERM" (which is the only
field being tokenised).
If I now query my index file for a term "6/12" for instance, I get back
only ONE result
SCOREDESCRIPTIONSTATUSCONCEPTID
