Phew :)
Thanks for bringing closure!
Mike
On Fri, Nov 13, 2009 at 5:22 AM, Benjamin Heilbrunn wrote:
> Hello,
>
> sorry for causing inconvenience.
> It was my mistake and i wasn't able to reproduce it completely this morning.
>
> My testcase was a little to complex and there were two or three b
Hello,
sorry for causing inconvenience.
It was my mistake and i wasn't able to reproduce it completely this morning.
My testcase was a little to complex and there were two or three bugs /
false assumptions which made it look to me like i explained above.
Benjamin
--
On Thu, Nov 12, 2009 at 5:28 PM, Uwe Schindler wrote:
> Mike: What was the reason for this change?
We first thought this (visiting segments from largest to smallest
size) improved performance, but, then we decided a better optimization
was for Collectors to save tie breaking by knowing the docID
: Thursday, November 12, 2009 11:15 PM
> > To: java-user@lucene.apache.org
> > Subject: Re: docBase Parameter in Collector.setNextReader
> >
> > Yes it should be 0 and 5.
> >
> > I'm not sure what would cause 0 and 0, offhand.
> >
> > Can you make
11:15 PM
> To: java-user@lucene.apache.org
> Subject: Re: docBase Parameter in Collector.setNextReader
>
> Yes it should be 0 and 5.
>
> I'm not sure what would cause 0 and 0, offhand.
>
> Can you make a small standalone test case showing it?
>
> Mike
&g
Yes it should be 0 and 5.
I'm not sure what would cause 0 and 0, offhand.
Can you make a small standalone test case showing it?
Mike
On Thu, Nov 12, 2009 at 4:25 PM, Benjamin Heilbrunn wrote:
> Hello everyone,
>
> I'm a little bit confused about the docBase parameter of
> Collector.setNextRead
Hello everyone,
I'm a little bit confused about the docBase parameter of
Collector.setNextReader.
Imagine the following:
- Create new Index
- Index 5 docs
- Call IndexWriter.commit()
- Index 7 docs
- Call IndexWriter.commit()
- close Writer
Now I have a 2-segment index right?
I have
