[
https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765076#action_12765076
]
Aytek Ekici edited comment on SOLR-236 at 10/13/09 6:48 AM:
------------------------------------------------------------
Hi all,
Just applied "field-collapse-5.patch" and i guess there are problems with
filter queries.
Here it is:
1- select?q=*:*&fq=lat:[37.2 TO 39.8]
numFound: 6284
2- select?q=*:*&fq=lng:[24.5 TO 29.9]
numFound: 16912
3- select?q=*:*&fq=lat:[37.2 TO 39.8]&fq=lng:[24.5 TO 29.9]
numFound: 19419
4- When using "q" instead of "fq" which is:
select?q=lat:[37.2 TO 39.8] AND lng:[24.5 TO 29.9]
numFound: 3777 (which is the only correct number)
The thing is, as i understand, instead of applying "AND" for each filter query
it applies "OR". Checked select?q=lat:[37.2 TO 39.8] OR lng:[24.5 TO 29.9]
numFound: 19419 (same as 3rd one)
Any idea how to fix this?
Thx.
was (Author: aytek):
Hi all,
Just applied "field-collapse-5.patch" and i guess there are problems with
filter queries.
Here it is:
1- http://10.231.14.252:8080/myindex/select?q=*:*&fq=lat:[37.2 TO 39.8]
numFound: 6284
2- http://10.231.14.252:8080/myindex/select?q=*:*&fq=lng:[24.5 TO 29.9]
numFound: 16912
3- http://10.231.14.252:8080/myindex/select?q=*:*&fq=lat:[37.2 TO
39.8]&fq=lng:[24.5 TO 29.9]
numFound: 19419
4- When using "q" instead of "fq" which is
http://10.231.14.252:8080/myindex/select?q=lat:[37.2 TO 39.8] AND lng:[24.5 TO
29.9]
numFound: 3777 (which is the only correct number)
The thing is, as i understand, instead of applying "AND" for each filter query
it applies "OR". Checked http://10.231.14.252:8080/myindex/select?q=lat:[37.2
TO 39.8] OR lng:[24.5 TO 29.9]
numFound: 19419 (same as 3rd one)
Any idea how to fix this?
Thx.
> 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-3.patch,
> field-collapse-4-with-solrj.patch, field-collapse-5.patch,
> field-collapse-5.patch, field-collapse-5.patch, field-collapse-5.patch,
> field-collapse-5.patch, field-collapse-5.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.
