[jira] [Comment Edited] (SOLR-5027) Field Collapsing PostFilter
[
https://issues.apache.org/jira/browse/SOLR-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13848876#comment-13848876
]
Deepak Mishra edited comment on SOLR-5027 at 12/16/13 7:06 AM:
---
Joel check the JIRA SOLR-5554 again. I have attached the details to reproduce
the error and the error log in FINE mode.
was (Author: deepakmishra117):
Joel check the JIRA again. I have attached the details to reproduce the error
and the error log in FINE mode.
Field Collapsing PostFilter
---
Key: SOLR-5027
URL: https://issues.apache.org/jira/browse/SOLR-5027
Project: Solr
Issue Type: New Feature
Components: search
Affects Versions: 5.0
Reporter: Joel Bernstein
Assignee: Joel Bernstein
Priority: Minor
Fix For: 4.6, 5.0
Attachments: SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch,
SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch,
SOLR-5027.patch, SOLR-5027.patch
This ticket introduces the *CollapsingQParserPlugin*
The *CollapsingQParserPlugin* is a PostFilter that performs field collapsing.
This is a high performance alternative to standard Solr field collapsing
(with *ngroups*) when the number of distinct groups in the result set is high.
For example in one performance test, a search with 10 million full results
and 1 million collapsed groups:
Standard grouping with ngroups : 17 seconds.
CollapsingQParserPlugin: 300 milli-seconds.
Sample syntax:
Collapse based on the highest scoring document:
{code}
fq=(!collapse field=field_name}
{code}
Collapse based on the min value of a numeric field:
{code}
fq={!collapse field=field_name min=field_name}
{code}
Collapse based on the max value of a numeric field:
{code}
fq={!collapse field=field_name max=field_name}
{code}
Collapse with a null policy:
{code}
fq={!collapse field=field_name nullPolicy=null_policy}
{code}
There are three null policies:
ignore : removes docs with a null value in the collapse field (default).
expand : treats each doc with a null value in the collapse field as a
separate group.
collapse : collapses all docs with a null value into a single group using
either highest score, or min/max.
The CollapsingQParserPlugin also fully supports the QueryElevationComponent
*Note:* The July 16 patch also includes and ExpandComponent that expands the
collapsed groups for the current search result page. This functionality will
be moved to it's own ticket.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-5027) Field Collapsing PostFilter
[
https://issues.apache.org/jira/browse/SOLR-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13848876#comment-13848876
]
Deepak Mishra commented on SOLR-5027:
-
Joel check the JIRA again. I have attached the details to reproduce the error
and the error log in FINE mode.
Field Collapsing PostFilter
---
Key: SOLR-5027
URL: https://issues.apache.org/jira/browse/SOLR-5027
Project: Solr
Issue Type: New Feature
Components: search
Affects Versions: 5.0
Reporter: Joel Bernstein
Assignee: Joel Bernstein
Priority: Minor
Fix For: 4.6, 5.0
Attachments: SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch,
SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch,
SOLR-5027.patch, SOLR-5027.patch
This ticket introduces the *CollapsingQParserPlugin*
The *CollapsingQParserPlugin* is a PostFilter that performs field collapsing.
This is a high performance alternative to standard Solr field collapsing
(with *ngroups*) when the number of distinct groups in the result set is high.
For example in one performance test, a search with 10 million full results
and 1 million collapsed groups:
Standard grouping with ngroups : 17 seconds.
CollapsingQParserPlugin: 300 milli-seconds.
Sample syntax:
Collapse based on the highest scoring document:
{code}
fq=(!collapse field=field_name}
{code}
Collapse based on the min value of a numeric field:
{code}
fq={!collapse field=field_name min=field_name}
{code}
Collapse based on the max value of a numeric field:
{code}
fq={!collapse field=field_name max=field_name}
{code}
Collapse with a null policy:
{code}
fq={!collapse field=field_name nullPolicy=null_policy}
{code}
There are three null policies:
ignore : removes docs with a null value in the collapse field (default).
expand : treats each doc with a null value in the collapse field as a
separate group.
collapse : collapses all docs with a null value into a single group using
either highest score, or min/max.
The CollapsingQParserPlugin also fully supports the QueryElevationComponent
*Note:* The July 16 patch also includes and ExpandComponent that expands the
collapsed groups for the current search result page. This functionality will
be moved to it's own ticket.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: SchemaDetails.txt
Query6.txt
Attaching required schema details, minimum query I took to get the error and
the error log I got in fine mode.
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: DetailedErrorOnQuery6.txt, Error On Query4, Query1.txt,
Query2.txt, Query3.txt, Query4.txt, Query5.txt, Query6.txt, SchemaDetails.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: DetailedErrorOnQuery6.txt
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: DetailedErrorOnQuery6.txt, Error On Query4, Query1.txt,
Query2.txt, Query3.txt, Query4.txt, Query5.txt, Query6.txt, SchemaDetails.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Comment Edited] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13848344#comment-13848344
]
Deepak Mishra edited comment on SOLR-5554 at 12/14/13 1:14 PM:
---
Attaching required schema details, minimum query (even without score) I took to
get the error and the error log I got in fine mode.
was (Author: deepakmishra117):
Attaching required schema details, minimum query I took to get the error and
the error log I got in fine mode.
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: DetailedErrorOnQuery6.txt, Error On Query4, Query1.txt,
Query2.txt, Query3.txt, Query4.txt, Query5.txt, Query6.txt, SchemaDetails.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-5554) Ordering Issue with
Deepak Mishra created SOLR-5554: --- Summary: Ordering Issue with Key: SOLR-5554 URL: https://issues.apache.org/jira/browse/SOLR-5554 Project: Solr Issue Type: Sub-task Reporter: Deepak Mishra -- This message was sent by Atlassian JIRA (v6.1.4#6159) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue with Collapse while using sort field min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Description:
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give document
in correct order but with NullPointerException in error and no facet (not the
one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Environment: Solr 4.6
Affects Version/s: 4.6
Summary: Ordering Issue with Collapse while using sort field min
max (was: Ordering Issue with )
Ordering Issue with Collapse while using sort field min max
---
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue with Collapse while using sort field min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Description:
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give document
in correct order but with NullPointerException in error and no facet (not the
one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
was:
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give document
in correct order but with NullPointerException in error and no facet (not the
one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Ordering Issue with Collapse while using sort field min max
---
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue with Collapse while using sort field min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: Query5.txt
Query4.txt
Query3.txt
Query2.txt
Query1.txt
Error On Query4
Ordering Issue with Collapse while using sort field min max
---
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Summary: Ordering Issue when Collapsing using min max (was: Ordering Issue
with Collapse while using sort field min max)
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: Query1.txt
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: (was: Query1.txt)
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: (was: Query5.txt)
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: Query5.txt
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: (was: Query2.txt)
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: (was: Query5.txt)
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: (was: Query1.txt)
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: Query5.txt
Query4.txt
Query3.txt
Query2.txt
Query1.txt
Error On Query4
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: (was: Error On Query4)
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: (was: Query4.txt)
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-5554) Ordering Issue when Collapsing using min max
[
https://issues.apache.org/jira/browse/SOLR-5554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Deepak Mishra updated SOLR-5554:
Attachment: (was: Query3.txt)
Ordering Issue when Collapsing using min max
Key: SOLR-5554
URL: https://issues.apache.org/jira/browse/SOLR-5554
Project: Solr
Issue Type: Sub-task
Components: search
Affects Versions: 4.6
Environment: Solr 4.6
Reporter: Deepak Mishra
Fix For: 4.6, 5.0
Attachments: Error On Query4, Query1.txt, Query2.txt, Query3.txt,
Query4.txt, Query5.txt
We faced the ordering issue without passing any sorting parameter and same
filters in both queries.
Query1
fq=
{!collapse field=company_id}
Query2
fq=
{!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in
fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give
document in correct order but with NullPointerException in error and no facet
(not the one in SOLR-5416).
facet.field=
{!ex=samsung}
brand
fq=
{!tag=samsung}
(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-5027) Field Collapsing PostFilter
[
https://issues.apache.org/jira/browse/SOLR-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13847343#comment-13847343
]
Deepak Mishra commented on SOLR-5027:
-
Joel, I created a new JIRA and attached the queries in SOLR-5554
Field Collapsing PostFilter
---
Key: SOLR-5027
URL: https://issues.apache.org/jira/browse/SOLR-5027
Project: Solr
Issue Type: New Feature
Components: search
Affects Versions: 5.0
Reporter: Joel Bernstein
Assignee: Joel Bernstein
Priority: Minor
Fix For: 4.6, 5.0
Attachments: SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch,
SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch,
SOLR-5027.patch, SOLR-5027.patch
This ticket introduces the *CollapsingQParserPlugin*
The *CollapsingQParserPlugin* is a PostFilter that performs field collapsing.
This is a high performance alternative to standard Solr field collapsing
(with *ngroups*) when the number of distinct groups in the result set is high.
For example in one performance test, a search with 10 million full results
and 1 million collapsed groups:
Standard grouping with ngroups : 17 seconds.
CollapsingQParserPlugin: 300 milli-seconds.
Sample syntax:
Collapse based on the highest scoring document:
{code}
fq=(!collapse field=field_name}
{code}
Collapse based on the min value of a numeric field:
{code}
fq={!collapse field=field_name min=field_name}
{code}
Collapse based on the max value of a numeric field:
{code}
fq={!collapse field=field_name max=field_name}
{code}
Collapse with a null policy:
{code}
fq={!collapse field=field_name nullPolicy=null_policy}
{code}
There are three null policies:
ignore : removes docs with a null value in the collapse field (default).
expand : treats each doc with a null value in the collapse field as a
separate group.
collapse : collapses all docs with a null value into a single group using
either highest score, or min/max.
The CollapsingQParserPlugin also fully supports the QueryElevationComponent
*Note:* The July 16 patch also includes and ExpandComponent that expands the
collapsed groups for the current search result page. This functionality will
be moved to it's own ticket.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-5027) Field Collapsing PostFilter
[
https://issues.apache.org/jira/browse/SOLR-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846229#comment-13846229
]
Deepak Mishra commented on SOLR-5027:
-
Hi Joel
I context with the Shruti's comment. We faced the ordering issue without
passing any sorting parameter and same filters in both queries.
Query1
fq={!collapse field=company_id}
Query2
fq={!collapse field=comany_id min=price}
Query3
For debugging Query2, we added score field in fl=score,offering_id,company_id...
That actually solved the document order issue
Query4
But when we passed selective exclude in facet field of Query3, it give document
in correct order but with NullPointerException in error and no facet (not the
one in SOLR-5416).
facet.field={!ex=samsung}brand
fq={!tag=samsung}(brand:samsung)
The error is
NullPointerException at
org.apache.solr.search.CollapsingQParserPlugin$FloatValueCollapse.collapse(CollapsingQParserPlugin.java:852)
Query5
Removing score from fl in Query 4 removes the error
Field Collapsing PostFilter
---
Key: SOLR-5027
URL: https://issues.apache.org/jira/browse/SOLR-5027
Project: Solr
Issue Type: New Feature
Components: search
Affects Versions: 5.0
Reporter: Joel Bernstein
Assignee: Joel Bernstein
Priority: Minor
Fix For: 4.6, 5.0
Attachments: SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch,
SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch, SOLR-5027.patch,
SOLR-5027.patch, SOLR-5027.patch
This ticket introduces the *CollapsingQParserPlugin*
The *CollapsingQParserPlugin* is a PostFilter that performs field collapsing.
This is a high performance alternative to standard Solr field collapsing
(with *ngroups*) when the number of distinct groups in the result set is high.
For example in one performance test, a search with 10 million full results
and 1 million collapsed groups:
Standard grouping with ngroups : 17 seconds.
CollapsingQParserPlugin: 300 milli-seconds.
Sample syntax:
Collapse based on the highest scoring document:
{code}
fq=(!collapse field=field_name}
{code}
Collapse based on the min value of a numeric field:
{code}
fq={!collapse field=field_name min=field_name}
{code}
Collapse based on the max value of a numeric field:
{code}
fq={!collapse field=field_name max=field_name}
{code}
Collapse with a null policy:
{code}
fq={!collapse field=field_name nullPolicy=null_policy}
{code}
There are three null policies:
ignore : removes docs with a null value in the collapse field (default).
expand : treats each doc with a null value in the collapse field as a
separate group.
collapse : collapses all docs with a null value into a single group using
either highest score, or min/max.
The CollapsingQParserPlugin also fully supports the QueryElevationComponent
*Note:* The July 16 patch also includes and ExpandComponent that expands the
collapsed groups for the current search result page. This functionality will
be moved to it's own ticket.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
