Hi all...
Just out of interest, why does field:* go via getWildcardQuery instead of
getPrefixQuery? It seems to me that it should be treated as a prefix of "",
but am I missing something important?
Also, I've noticed that although RangeQuery was optimised in a recent version
of Lucene, Prefix
Toke Eskildsen wrote:
== Average over the first 50.000 queries ==
metis_flash_RAID0_8GB_i37_t2_l21.log - 279.6 q/sec
metis_flash_RAID0_8GB_i37_t2_l23.log - 202.3 q/sec
metis_flash_RAID0_8GB_i37_v23_t2_l23.log - 195.9 q/sec
== Average over the first 340.000 queries ==
metis_flash_RAID0_8GB_i37
Indeed--this is why the associated parameter is called
maxAnalyzedChars in Solr.
-Mike
On 14-Jan-08, at 2:33 PM, Mark Miller wrote:
I think your right, and thats not the only place...the whole
handling of maxDocBytesToAnalyze in the main Highlighter class
shares this issue. I guess the id
Hi,
I am slightly confused.
The following code generates the output below.
Document doc = hits.doc(i);
System.out.println(doc.getFields());
Field f = doc.getField("Text");
System.out.println(f);
TokenStream ts = f.tokenStreamValue();
System.out.println(ts);
while (true){
Token token =
On Tue, 2008-01-22 at 03:08 -0800, Michael Busch wrote:
> OK, then Yonik might be right about the multi-level skiplists code which
> is new in 2.2. I'd love to see the performance numbers of the same index
> built with 2.3, if possible? You could simply migrate it to 2.3 by using
> IndexWriter.addI
Thanks Michael for your answer :)
Actually writer.addIndexesNoOptimize method can not help us because our
aim is to split indexes rather than to merge them. But you information
about setting autoCommit=true is very helpful for us because so we will
avoid sharing of stored fields and will be ab
