: I'm trying to look at the source of the classes in
: org.apache.lucene.misc. I couldn't find the package in the latest
: nightly build. Where should I be looking?
you want to look at contrib/miscellaneous
-Hoss
-
To unsubsc
Thinking about this a little more: my short term advice to you would be to
use FieldCache.getCustom with your own SortComparator that just returns
the Float/Int value parsed fro mthe string ... the Comparable[] should
default to "null" for any doc that doesn't have a value for the field, so
you'll
: The default should be 0 to keep being backwards compatible. Then just
: provide a means to change that setting. So for my code I just could add:
: setInitialValue(Float.NEGATIVE_INFINITY); for example.
: Being the INITIAL_VALUE thingy set initially to 0. That would be backwards
: compatible
: > your Scorer.next method should be skipping over documents that you do not
: > consider "matches" to your search.
: >
: But, since the value on the float[] is the same regardless it has a field
: with value '0' and has no field, how can i tell one from another?
Well the FieldCache default valu
: Sorry for the rant... I guess my short answer is that I don't have an
: opinion on adding another type-safe constant TOKENIZED_NO_NORMS
: because I don't like the whole scheme.
agreed ... if people feel there is enough of a disconnect between the
options available as constructor args and the op
Excellent! I'll give it a whirl in the morning. This may keep me from having
to rebuild my index as well, oh joy!
Thanks
Erick
On 2/15/07, Mark Miller <[EMAIL PROTECTED]> wrote:
Here is my initial attempt...I believe it might be sufficient:
import org.apache.lucene.index.IndexReader;
import o
Here is my initial attempt...I believe it might be sufficient:
import org.apache.lucene.index.IndexReader;
import org.apache.lucene.index.Term;
import org.apache.lucene.search.BooleanClause;
import org.apache.lucene.search.BooleanQuery;
import org.apache.lucene.search.PhraseQuery;
import org.apac
Mark:
Thanks, that reassures me that I'm not hallucinating. If it gets on my
priority list I can certainly share the code, since I stole it in the first
place . I have a semi-solution for now that gets me out from under the
immediate problem, but it really wants a more robust solution than the on
Good catch Erick! I'll have to tackle this as well. Mark H is the
originator of that code so maybe he will chime in, but what I am think
is this:
In the getSpansFromBooleanquery, keep track of which clauses are
required. Then based on if any Spans are actually returned from
getSpansFromTerm f
On 2/15/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
the ideal way to do this might be to add a "getDefault()" method to the
IntParser and FloatParser interfaces ... but thta wouldn't be backwards
compatible.
Interfaces vs abstract classes again :-)
Users sometimes like interfaces better beca
I originally added it without an Index param at all.
I can't say I'm a fan of the way Field currently does things, and I
didn't want everyone to pay the price for yet more options.
Look at the code for the Field constructor:
public Field(String name, String value, Store store, Index index,
Term
Hi,
I'm trying to look at the source of the classes in
org.apache.lucene.misc. I couldn't find the package in the latest
nightly build. Where should I be looking?
Thank you,
Seeta Somagani
15 feb 2007 kl. 19.28 skrev Deepa Paranjpe:
I want to optimize maximally on the search time required by lucene
on over
~7M short documents. The queries that I deal are 6 to 7 tokens on an
average.
Load your FSDirectory to a RAMDirectory.
If you feel experimental you can take a look at
Hi all,
I want to understand how lucene searches its index -- does it load the whole
index into memory at once? Is there any way to make sure that it does so.
I want to optimize maximally on the search time required by lucene on over
~7M short documents. The queries that I deal are 6 to 7 tokens
I hope you're all following this old thread, because I've just run into
something I don't quite know what to do about with the SpansExtractor code
that I shamelessly stole.
Let's say my text is "a b c d e f g h" and my query is "a AND z". The
implementation I stole for SpansExtractor (mentioned s
On Fri, Jan 26, 2007, Otis Gospodnetic wrote about "Re: NO_NORMS and
TOKENIZED?":
> Funny, I was looking to do the same thing the other day and gave up thinking
> it wasn't possible, not being aware of setOmitNorms(). Yeah, a javadoc patch
> would be welcome.
>
> Otis
Before I go ahead and po
Le Jeudi 15 Février 2007 10:27, Chris Hostetter a écrit :
> : I wanted to implement my own query, query wich will be specific to my
> : application. The query I want to implement is in fact just a combinaison
> : of sevral already implemented queries. So acheive this, I do this kind of
>
> you can
Chris Hostetter wrote:
>
>
> : i suggest it could be defined a (e.g.) NOT_FOUND_FLOAT_VALUE,
> modifiable,
> : so it does not necessarily have to be 0. And used for initialise the
> array
> : of floats before processing (or do it on the loop if better performance
> can
> : be reached).
> :
Chris Hostetter wrote:
>
> your Scorer.next method should be skipping over documents that you do not
> consider "matches" to your search.
>
But, since the value on the float[] is the same regardless it has a field
with value '0' and has no field, how can i tell one from another?
Chris Hostet
: I wanted to implement my own query, query wich will be specific to my
: application. The query I want to implement is in fact just a combinaison of
: sevral already implemented queries. So acheive this, I do this kind of
you can probably achieve your goal by simply making MyQuery.rewrite return
Hi,
I wanted to implement my own query, query wich will be specific to my
application. The query I want to implement is in fact just a combinaison of
sevral already implemented queries. So acheive this, I do this kind of
things :
public class MyQuery extends Query {
private Query query;
pub
: The array of floats for the Float cache is not initialised. Which means that
: it will return '0.0' (not initialised) as the value for those documents that
: have a '0' as the value, as well as for those ones that do not have the
: field.
you may find this class interesting...
http://svn.apache
: I have been diving into the code and I don't see why the class
: FieldCacheImpl is not extendible. It is not defined as a public class...
: though, I would like to be able to subclass it to change a slight bit.
:
: Why is it defined like that?
I don't know that there is any particular reason ..
: I have created a Query that works for numerical max-min ranges, that may
: work for any Field specified.
: I have done that by extending Query, and creating own Weight and Scorer
: subclasses as well.
: So it works ... but I have problems when setting min or max boundary to 0:
: In this case, th
24 matches
Mail list logo