[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12501405
]
Ryan McKinley commented on SOLR-236:
------------------------------------
I just took a look at this using the example data:
http://localhost:8983/solr/select/?q=*:*&collapse.field=cat&collapse.max=1&collapse.type=normal&rows=10
<lst name="collapse_counts">
<str name="field">cat</str>
<lst name="doc">
<int>1</int>
<int name="1">2</int>
<int name="2">2</int>
<int name="4">1</int>
<int name="7">1</int>
</lst>
<lst name="count">
<int>1</int>
<int name="card">2</int>
<int name="drive">2</int>
<int name="hard">1</int>
<int name="music">1</int>
</lst>
</lst>
- - -
what is the "<int>1</int>" at the front of each response?
Perhaps the 'doc' results should be renamed 'offset' or 'index', and then have
another one named 'doc' that uses the uniqueKey as the index... this would be
useful to build a Map.
- - -
Also, check:
http://localhost:8983/solr/select/?q=*:*&collapse.field=cat&collapse.max=1&collapse.type=adjacent&rows=50
ArrayIndexOutOfBoundsException:
- - -
> You should add the following constraint on the wiki: The collapsing field
> must be un-tokenized.
Anyone can edit the wiki (you just have to make an account) -- it would be
great if you could help keep the page accurate / useful. JIRA discussion
comment trails don't work so well at that...
Re: tokenized... what about it does not work? Are the limitations an
different if it is mult-valued? Is it just that if any token matches within
the field it will collapse and that may or may not be what you expect?
- - -
Did you get a chance to look at the questions from the previous discussion? I
just noticed Yonik posted something new there:
http://www.nabble.com/result-grouping--tf2910425.html#a10959848
> 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.2
> Reporter: Emmanuel Keller
> Attachments: collapse_field.patch, collapse_field.patch,
> field_collapsing.patch, field_collapsing.patch, field_collapsing.patch,
> field_collapsing_1.1.0.patch, SOLR-236-FieldCollapsing.patch,
> SOLR-236-FieldCollapsing.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 (1.2)
> - "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.
