It's all in the analyzers. Depending upon which analyzer you use manythings
happen to the input stream. Casing is one example, but that's just
the simplest. Which is why it's so important to use the same analyzer
when indexing and querying unless you have a *very* good reason not to.
I'd really ad
Case?
Hmm. I thought it was case intensive.
I will re-index and revert all to lower case and see. The language is stored
as "English" not "english"
ian
P.S. Here's what I built with a basic understanding of Lucene.
http://BahaiResearch.com it's open source, ad-free. It allows people in 20
langu
Hm. Let's see the queries, and query.toString() may give
you some clues. I *suspect* that you really didn't index language.
Did you, perhaps, not re-index all your docs? Or use an analyzer
that didn't fold case when searching but did when searching (or
vice-versa)?
It's *possible* that you've
I have created an index and each document has a contents field and a
language field.
contents has the flags: Indexed Tokenized Stored Vector
language has the flags: Indexed Stored
In luke I can search contents fine, but when I try to search the field
language, I never ever get results.
Every doc
