Thanks, Tomas. Yes we are planning to keep a "current" flag in the most
current document. But there are cases where, for a given user, the most
current document is not that one, because they only have access to some
older documents.
I took a look at http://wiki.apache.org/solr/FieldCollapsing and it
seems as if it will do what we need here. My one concern is that it
might not be efficient at computing group.ngroups for a very large
number of groups, which we would ideally want. Is that something I
should be worried about?
-Mike
On 08/01/2011 10:08 AM, Tomás Fernández Löbbe wrote:
Hi Michael, I guess this could be solved using grouping as you said.
Documents inside a group can be sorted on a field (in your case, the version
field, see parameter group.sort), and you can show only the first one. It
will be more complex to show facets (post grouping faceting is work in
progress but still not committed to the trunk).
I would be easier from the Solr side if you could do something at index
time, like indicating which document is the "current" one and which one is
an old one (you would need to update the old document whenever a new version
is indexed).
Regards,
Tomás
On Mon, Aug 1, 2011 at 10:47 AM, Mike Sokolov<soko...@ifactory.com> wrote:
A customer has an interesting problem: some documents will have multiple
versions. In search results, only the most recent version of a given
document should be shown. The trick is that each user has access to a
different set of document versions, and each user should see only the most
recent version of a document that they have access to.
Is this something that can reasonably be solved with grouping? In 3.x? I
haven't followed the grouping discussions closely: would someone point me in
the right direction please?
--
Michael Sokolov
Engineering Director
www.ifactory.com
