What do you mean not something I can plug in on top of my original query?
Do you mean that you can't do it like the more complex example in the class
you posted earlier in the thread, where you take a linear combination of the
MapString, Float -based score, and the regular text score?
Another
Michael McCandless wrote:
On the indexing side you do this:
doc.add(new NumericField(price).setDoubleValue(19.99));
The NumericField is not stored by default (there's also a ctor to
specify Store.YES or Store.NO).
If the numeric field is not being used in a range query, how is it
being
As we told you before. The default QueryParser has no support fro
NumericField (as it doesn't know the schema). To get it running, subclass it
and overwrite newRangeQuery method to create a NumericRangeQuery for field
names that are indexed using NumericField.
The recommended way is to
Uwe Schindler wrote:
As we told you before. The default QueryParser has no support fro
NumericField (as it doesn't know the schema). To get it running, subclass it
and overwrite newRangeQuery method to create a NumericRangeQuery for field
names that are indexed using NumericField.
Hi, yes I
Man, this thread really went south. Anyhow, I have a few questions about Zoie:
* How many nodes are you using to support the speeds you desire at LI?
* Am I wrong to assume that the RAMDir holds the entire index - just as the
FSDir? Or does RAMDir only hold a portion of the index that hasn't
Hi Eric:
I regret the direction the thread has taken and partly take responsibility
for it...
As to your question:
We have 2 nodes per commodity server, each holding 5 million docs (although
given the numbers we are seeing, we think we were a bit too conservative,
and may increase to 10). In
Eric:
For more specific Zoie questions, let's move it to the zoie discussion
group instead.
Thanks
-John
On Sun, Oct 11, 2009 at 2:31 PM, John Wang john.w...@gmail.com wrote:
Hi Eric:
I regret the direction the thread has taken and partly take responsibility
for it...
As to your
Ok nevermind actually - the simultaneous indexing was something done in zoie
1.3,
and was changed in 1.4 to addIndexesNoOptimize() on the RAMDirectory indexes
as soon as they are big enough.
It's still true that you can throw away the RAMDirectory once the disk index
is
reopened though.
-jake
On Sun, Oct 11, 2009 at 9:10 AM, Jake Mannix jake.man...@gmail.com wrote:
What do you mean not something I can plug in on top of my original query?
Do you mean that you can't do it like the more complex example in the class
you posted earlier in the thread, where you take a linear combination
Hi guys:
The new FieldComparator api looks really scary :)
But after some perf testing with numbers I'd like to share, I guess it
is worth it:
HW: Mac Pro with 16G memory
jvm: 1.6.0_13
jvm arg: -Xms1g -Xmx1g -server
setup
index:
1M docs even split into 8 segments (to make sure the test
10 matches
Mail list logo