Thanks Toke. Very descriptive. A few more questions about your SSD
drive(s)
- what is its current size
- do you project any growth in your index size
- if yes then how do you plan to correlate that with your hardware
needs
Thanks again
Eugene.
-Original Message-
From: Toke Eskildsen
On Tue, 2010-10-26 at 14:27 +0200, Lucene wrote:
> In simple words, I need facet on the next word given a target word.
How large do you expect the documents to be and how many hits do you
need to process? If both are low, this seems to be a fairly straight
forward iteration with a HashMap to colle
See the Collocation stuff here https://issues.apache.org/jira/browse/LUCENE-474
- Original Message
From: Lucene
To: java-user@lucene.apache.org
Sent: Tue, 26 October, 2010 13:27:06
Subject: Next Word - Any Suggestions?
Am about to implement a custom query that is sort of mash-up of Fac
Am about to implement a custom query that is sort of mash-up of Facets,
Highlighting, and SpanQuery - but thought I'd see if anyone has done
anything similar.
In simple words, I need facet on the next word given a target word.
For example, if my index only had the following 5 documents (co
On Tue, 2010-10-26 at 02:16 +0200, Kovnatsky, Eugene wrote:
> I am trying to get some information on what enterprise hardware folks
> use out there. We are using Lucene extensively. Our total catalogs size
> is roughly 50GB between roughly 8 various catalogs, 2 of which take up
> 60-70% of this siz
Thx Uwe,
after sleeping over the problem...
The solution just hit me ;)
I index a double for the Numeric field but my Sortfield was setup as a float.
(Maybe this is something for a FAQ for NumericFields)
Thx
Uwe
-Ursprüngliche Nachricht-
Von: Uwe Schindler [mailto:u...@thetaphi.de]
Ges
This happens if your field still contains other value types in this field,
maybe from deleted documents. The problem is that even if no document
contains the old field encoding anymore, it could still be leftover terms in
terms index. So the FieldCache code loads the terms (even if no longer
docume
