: I override the seek() and next() methods of FilterTermDocs.
: The problem is the although my seek() method is being called,
: my next() method is not. Thus I never get to iterate through
: my list, and only receive results corrasponding to its first
: element.
It's pretty much impossible to gu
right now there is field level search avilable.
But if we dont want to search on field but on the whole document then to the
query parseer the whole contet is to be passed.
If we append the titles (captions or fields) to say
index content(which is having all the captions or fields)
I already have this implemented with a filter. Its working alright, but
sends my running time
from .1 sec to .4 sec - thats no big deal now but we hope to eventually grow
the archive to
an insanely large size. Besides, I think the FilterIndexReader is a
powerfull tool, and I'd
like to get it worki
Wouldn't it be easier to just make a Filter? That's what they were
intended for.
Especially, if by "certain set", you mean that these are pre-defined
values, you could create your filters at start-up time and use
CachingWrapperFilter to keep them around.
Either way, I suspect it would be much si
I am trying to use a Filter Index Reader to
provide access only to the subset of my archive
for which a certain field contains one of a given
list of values.
The idea is to create a special term for this field
that means 'any term in the list', and add an 'AND'
clause to every query, to enforce t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
at the open-source project mmm we provide a generic search-solution based on
lucene:
http://m-m-m.sourceforge.net/maven/mmm-search/
This covers the typical gaps like indexing binary documents as well as providing
an example web-frontend w
Maybe I'm missing the boat, but I don't understand why TermEnum doesn't
work for you.
Try something like...
TermEnum te = this.reader.terms();
te.skipTo(new Term("keyword", ""));
while (te.next()) {
Term term = te.term();
if (! term.field().equals("keywor
Erick Erickson wrote:
Um, to return all counts of all terms in a field, what other option
*is* there except to walk the whole thing?
Have you looked at TermEnum, TermDocs, and TermFreqVector?
For that matter, TermPositionVector might also be of some use.
It would be easier to provide some hel
See below...
On 6/8/07, Chris Lu <[EMAIL PROTECTED]> wrote:
Thanks to all who answered with their experience and insights!
LUCENE-625 is very interesting, but not sure about the scalability.
"Begin completion only with 3 letters or more" is reasonable for
special cases, but not ideal. What I w
Um, to return all counts of all terms in a field, what other option
*is* there except to walk the whole thing?
Have you looked at TermEnum, TermDocs, and TermFreqVector?
For that matter, TermPositionVector might also be of some use.
It would be easier to provide some help if you
1> mentioned wha
10 matches
Mail list logo