Truly I am new to Lucene. That's the missing part ... I'm looking at the
stored values and not the indexed terms.
Mark
On 9/17/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
1) maybe you didn't really use StandardAnalyzer when the index was built?
2) keep in mind there is a differnece between
You probably want to tak a closer look at the StandardAnalyzer. It uses
StandardTokenizer and StandardFilter. From the javadoc
When I first started with Lucene, I was surprised that StandardAnalyzer did
the tricks it does. I quickly found that, especially when starting out, I
got more int
: index using the StandardAnalyzer, the docs are transformed using that
: analyzer then written to the index post transformation. So stop words or
: things like apostrophes would be removed.
if the analyzer used behaves that way, then yes -- the indexed terms will
remove those things.
: "Scott's
That question was badly worded. I was trying to ask that when I write an
index using the StandardAnalyzer, the docs are transformed using that
analyzer then written to the index post transformation. So stop words or
things like apostrophes would be removed.
"Scott's Lawn and Garden Care" bec
: One more question about IndexWriters (maybe I don't deserve an answer here
: :-) ) I assume that the Analyzer used is applied and written to the
: index per field. So if I wanted one for Snowball or Stemming I'd have to
: write multiple indexes? I'm a bit confused as to how the Stemmed q
Ok guys ... you're going to want to yield a big stick to me. The problem
was my HItCollector, I wasn't actually passing it to my searcher. Yes
somewhere in my testing I had commented out that code and it was making it
look like I wasn't getting hits.
One more question about IndexWriters (maybe
Well, I'm puzzled as well, in my simple examples I just ran, the AND
operator behaves just fine, but that was using StandardAnalyzer. So it's
almost certain we're not talking about the same thing ...
So, I guess I have a couple of suggestions:
1> Try your query without the stemmingAnalyzer. Try
I am new to Lucene so I'll admit I am confused by a few things. I'm using
an index which was built with the StandardAnalyzer. I have verified this by
using an IndexReader to read the docs back out ... Antiques is not Antiq in
the index. So according to this note in the Lucene docs I would assu
3 docs with one field each in index:
-
french beast stone
crazy rolling stone
rolling stone done in by coconut
3 searches, default op set as AND
-
search("coconut stone");
search("coconut OR stone");
search("coconut AND stone
Are you really, really sure that your *analyzer* isn't automatically
lower-casing your *query* and turning "french AND antiques" into "french and
antiques", then, as Chris says, treating "and" as a stop word?
The fact that your parser transforms "antiques" into "antiqu" leads me to
suspect that t
When I use "french AND antiques" I get documents like this :
score: 1.0, boost: 1.0, cont: French Antiques
score: 0.23080501, boost: 1.0, cont: FRENCH SEPTIC
score: 0.23080501, boost: 1.0, cont: French & French Septic
score: 0.20400475, boost: 1.0,id: 25460, cont: French & Associates
As in the f
: Why does my query "french AND antiques" work the way I expect using this
: code:
can you be more specific about what it is you "expect", and what exactly
serachTerms is in your examples? (presumably it's a string, is it the
string "french AND antiques" ... are you sure it's not "french and
ant
Why does my query "french AND antiques" work the way I expect using this
code:
stemParser = new QueryParser("contents", stemmingAnalyzer);
Query query = stemParser.parse(searchTerms);
Hits docHits = searcher.search(query);
Debug from query shows: contents:french contents:antiqu ... I would h
13 matches
Mail list logo
