That's right. I just had another decorator which was not adapted for
the new API. My fault ..
Thanks,
Jerome.
2009/8/18 Mark Miller :
> I'm pretty sure one of them is called. In the version you have:
>
> public void search(Query query, HitCollector results)
> throws IOException {
> search(c
I'm pretty sure one of them is called. In the version you have:
public void search(Query query, HitCollector results)
throws IOException {
search(createQueryWeight(query), null, new
HitCollectorWrapper(results));
}
protected QueryWeight createQueryWeight(Query query) throws IOExceptio
Hi Mark,
Thanks for clarifying this. So should I keep both sets of method
implemented? I guess it won't hurt when solr trunk will use the
updated version of lucene without those methods.
What I don't get is that neither my createWeight or createQueryWeight
methods seem to be called when I call
r
You have run into some stuff that has been somewhat rolled back in Lucene.
QueryWieght, and the methods it brought have been reverted.
Shortly (when Solr trunk updates Lucene), Solr will go back to just
createWeight and weight.
The main change that will be left is that Weight will be an abstr
Hi all,
I have a custom search component which uses a query I wrote.
Basically, this Query (called DocSetQuery) is a Query decorator that
skips any document which is not in a given document set. My code used
to work perfectly in solr 1.3 but in solr 1.4, it seems that my
DocSetQuery has lost all
