[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12716373#action_12716373
]
Stephen Weiss commented on SOLR-236:
------------------------------------
The problem sounds very familiar to me, I remember going through something
similar when I was first trying to get the patch to work. My configuration
ended up being:
<searchComponent name="collapse"
class="org.apache.solr.handler.component.CollapseComponent" />
<requestHandler name="standard" class="solr.StandardRequestHandler">
<!-- default values for query parameters -->
<lst name="defaults">
<str name="echoParams">explicit</str>
<!--
<int name="rows">10</int>
<str name="fl">*</str>
<str name="version">2.1</str>
-->
</lst>
<arr name="components">
<str>query</str>
<str>facet</str>
<str>collapse</str>
<str>mlt</str>
<str>highlight</str>
<str>debug</str>
</arr>
</requestHandler>
All I remember is if I didn't have that <arr name="components"> section
arranged exactly like that (even if I rearranged other items without
rearranging the "collapse" part), either 1) faceting would completely stop
working correctly at all, giving me totally bogus numbers or 2) I would get
something a lot like the error described above and nothing would work at all.
However, I'm using an older version of the patch
(collapsing-patch-to-1.3.0-ivan_3.patch) so it's totally possible that this has
nothing to do with that.
On that note... have people found in general that the newer versions of the
patch give any particular benefits in particular? I saw someone say that the
latest patches were faster but I wasn't sure if they were faster in all cases
or only when not sorting (we always sort so if it's only for unsorted sets it
doesn't do us much good).
> Field collapsing
> ----------------
>
> Key: SOLR-236
> URL: https://issues.apache.org/jira/browse/SOLR-236
> Project: Solr
> Issue Type: New Feature
> Components: search
> Affects Versions: 1.3
> Reporter: Emmanuel Keller
> Fix For: 1.5
>
> Attachments: collapsing-patch-to-1.3.0-dieter.patch,
> collapsing-patch-to-1.3.0-ivan.patch, collapsing-patch-to-1.3.0-ivan_2.patch,
> collapsing-patch-to-1.3.0-ivan_3.patch, field-collapse-solr-236-2.patch,
> field-collapse-solr-236.patch, field-collapsing-extended-592129.patch,
> field_collapsing_1.1.0.patch, field_collapsing_1.3.patch,
> field_collapsing_dsteigerwald.diff, field_collapsing_dsteigerwald.diff,
> field_collapsing_dsteigerwald.diff, SOLR-236-FieldCollapsing.patch,
> SOLR-236-FieldCollapsing.patch, SOLR-236-FieldCollapsing.patch,
> solr-236.patch, SOLR-236_collapsing.patch, SOLR-236_collapsing.patch
>
>
> This patch include a new feature called "Field collapsing".
> "Used in order to collapse a group of results with similar value for a given
> field to a single entry in the result set. Site collapsing is a special case
> of this, where all results for a given web site is collapsed into one or two
> entries in the result set, typically with an associated "more documents from
> this site" link. See also Duplicate detection."
> http://www.fastsearch.com/glossary.aspx?m=48&amid=299
> The implementation add 3 new query parameters (SolrParams):
> "collapse.field" to choose the field used to group results
> "collapse.type" normal (default value) or adjacent
> "collapse.max" to select how many continuous results are allowed before
> collapsing
> TODO (in progress):
> - More documentation (on source code)
> - Test cases
> Two patches:
> - "field_collapsing.patch" for current development version
> - "field_collapsing_1.1.0.patch" for Solr-1.1.0
> P.S.: Feedback and misspelling correction are welcome ;-)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
