Phew, thanks for bringing closure!
Mike McCandless
http://blog.mikemccandless.com
On Fri, Mar 9, 2012 at 8:52 AM, Grzegorz Tańczyk wrote:
> Hello,
>
> I found the problem and it was my misunderstanding. I didn't get first
> documents in every group, because some of head documents didn't match g
Hello,
I found the problem and it was my misunderstanding. I didn't get first
documents in every group, because some of head documents didn't match
given query. I made a wrong assumption that I can sort between all
documents within group.
--
Regards,
Grzegorz
On Thu, Mar 8, 2012 at 7:22 AM, Grzegorz Tańczyk
wrote:
> Hello,
>
> Thanks for reply, I can find first document from group using non grouping
> search.
OK, so the index seems ok.
> To be sure about this I deleted index and indexed only first 100 groups
> which gives around 2300 documents and I
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
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
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,
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
