Hello,
I am using BlockGroupingCollector for first time and I have some small
problem with it. Indexing code is pretty much copy of the one from docs.
Searching looks like this:
Filter groupEndFilter = new CachingWrapperFilter(new
QueryWrapperFilter(new TermQuery(new Term("la
Hmm... that doesn't sound good.
Is the issue repeatable once it happens? And, when it happens, can
you verify that the index is corrrect (eg, the missing doc is
retrievable by non-grouped searches)? This way we can isolate the
issue to the search-side.
Can you boil it down to a small test case?
Hello,
Thanks for reply, I can find first document from group using non
grouping search.
To be sure about this I deleted index and indexed only first 100 groups
which gives around 2300 documents and I see the problem on at least half
of groups. No problem in finding first documents normally
> I think a good question is whether you are really seeing performance issues
> due to the 1/3 deleted-
> but-not-yet-reclaimed documents...
No, I'm NOT worried about performance. I've got the message about optimize().
I was just looking for something I might do maybe once or twice a year when
Hi,
> Interesting coincidence, just last night one of our in-house indexes must
have
> decide it could use some merging and dropped 5 segments (of ~30+) and 4-5
> GB (of a total ~20-25 GB). So it was great to see it in action.
>
> I'm in no hurry, but I'll be eventually looking into using
TieredM
> Uwe Schindler wrote:
> TieredMP is already the default in Lucene 3.5, unless you explicitely set
> another one!
>
I was going to add the detail that I was running 3.4 at the moment (I'm looking
to upgrade very soon) and thought
LogByteSizeMergePolicy was the default there, but I am wrong th
Hello,
Thanks for reply, I can find first document from group using non
grouping search.
To be sure about this I deleted index and indexed only first 100 groups
which gives around 2300 documents and I see the problem on at least half
of groups. No problem in finding first documents normally
On 03/02/2012 15:01, Paul Taylor wrote:
Using Lucene 3.5, I created a query parser based on the dismax parser
but in order to get matches on misspellings ecetra I additionally do a
fuzzy search and a wildcard search
http://svn.musicbrainz.org/search_server/trunk/servlet/src/main/java/org/mu
