On Thu, Apr 5, 2012 at 3:31 PM, Ivan Brusic wrote:
> On Thu, Apr 5, 2012 at 11:36 AM, Michael McCandless
> wrote:
>> I'm assuming this is a "build once and never change" index...? Else,
>> it sounds like you should never run forceMerge...
>
> Correct. The forceMerge was merely to preserve the p
Hi all,What would be the best approach for a custom scoring that requires a "global" view of the result set. For example, I have a field call "color" and I would like to have constraints that there are at most 3 docs with color:red, 4 docs with color:blue in the first 16 hits. And the items should
> To enforce creation of CFS files, you have to set the CFS percentage to 100%
> (1.0) in the MergePolicy: http://goo.gl/X9pF3, http://goo.gl/QFKGf By default
> Lucene only created CFS files, if the segment size is larger than 10% of the
> whole index.
Sorry, other way round of course. Large segme
To enforce creation of CFS files, you have to set the CFS percentage to 100%
(1.0) in the MergePolicy: http://goo.gl/X9pF3, http://goo.gl/QFKGf
By default Lucene only created CFS files, if the segment size is larger than
10% of the whole index.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28
Hey, do you get multiple files per segment or multiple files per index?
The compoundfile system writes a .cfs file (and a .cfe file in trunk)
per segment. So if you are seeing multiple .cfs fiels Lucene is
actually doing what you want. If there are files like .fdt/fdx or
tii/tis then the segment is
Hi guys,
I am still learning Lucene, and I had a very weird problem yesterday
that no matter what I did, I always got multifiles not compound file. By
default, Lucene use compound file, but I just got this weird problem,
even if I used setUseCompoundFile(true) explicitly... And my code is
actually
