[jira] [Commented] (SOLR-5027) Field Collapsing PostFilter
[
https://issues.apache.org/jira/browse/SOLR-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13854870#comment-13854870
]
Phil John commented on SOLR-5027:
-
Hi Joel,
Thanks for the clarification - I wondered if it would be in the expander, but
came away a bit confused as to what that would end up doing.
Nice to know it'll come, and as a workaround we can just query for counts from
our DB grouped by collapse key until it lands in trunk.
Thanks,
Phil.
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=13853820#comment-13853820
]
Phil John commented on SOLR-5027:
-
The one thing this doesn't seem to do, which the current field collapsing
solution does, is say how many items there are in each group - which is useful
if you want to display the top result, but also have a link saying X other
available. Our use case is collapsing down multiple manifestations of a
bibliographic work (i.e. multiple editions of the same work), so with the
grouping feature we get a count back of the size of the group and can go 5
other editions also available and then link to a search on the key we
collapsed by.
Is this planned, or will that come in the more generic aggregation support
planned for 5.0?
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-4629) Stronger standard replication testing.
[ https://issues.apache.org/jira/browse/SOLR-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13610112#comment-13610112 ] Phil John commented on SOLR-4629: - Just to add, I'm seeing this as well on our setup (1 master, 2 slaves, traditional replication setup rather than solrcloud). Stronger standard replication testing. -- Key: SOLR-4629 URL: https://issues.apache.org/jira/browse/SOLR-4629 Project: Solr Issue Type: Test Components: replication (java) Reporter: Mark Miller Assignee: Mark Miller Fix For: 4.3, 5.0, 4.2.1 I added to these tests recently, but there is a report on the list indicating we may still be missing something. Most reports have been positive so far after the 4.2 fixes, but I'd feel better after adding some more testing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Issue Comment Deleted] (SOLR-4629) Stronger standard replication testing.
[ https://issues.apache.org/jira/browse/SOLR-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil John updated SOLR-4629: Comment: was deleted (was: Just to add, I'm seeing this as well on our setup (1 master, 2 slaves, traditional replication setup rather than solrcloud). ) Stronger standard replication testing. -- Key: SOLR-4629 URL: https://issues.apache.org/jira/browse/SOLR-4629 Project: Solr Issue Type: Test Components: replication (java) Reporter: Mark Miller Assignee: Mark Miller Fix For: 4.3, 5.0, 4.2.1 I added to these tests recently, but there is a report on the list indicating we may still be missing something. Most reports have been positive so far after the 4.2 fixes, but I'd feel better after adding some more testing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4573) oejh.HttpGenerator:Ignoring extra content when accessing Solr HTTP Admin Console in Solr Cloud example
[ https://issues.apache.org/jira/browse/SOLR-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13604399#comment-13604399 ] Phil John commented on SOLR-4573: - You're welcome. oejh.HttpGenerator:Ignoring extra content when accessing Solr HTTP Admin Console in Solr Cloud example -- Key: SOLR-4573 URL: https://issues.apache.org/jira/browse/SOLR-4573 Project: Solr Issue Type: Bug Components: SolrCloud, web gui Affects Versions: 4.2 Environment: Windows x64 java version 1.7.0_11 Java(TM) SE Runtime Environment (build 1.7.0_11-b21) Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode) Reporter: Phil John Assignee: Mark Miller Priority: Minor Fix For: 4.3, 5.0 When running the example config included in the Solr distribution based on the instructions here: http://wiki.apache.org/solr/SolrCloud#Example_A:_Simple_two_shard_cluster Any requests to pages in the web gui cause a warning log message to be raised on Jetty's STDOUT 2013-03-13 19:52:45.827:WARN:oejh.HttpGenerator:Ignoring extra content followed by the content of the file being served. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-4573) oejh.HttpGenerator:Ignoring extra content when accessing Solr HTTP Admin Console in Solr Cloud example
[ https://issues.apache.org/jira/browse/SOLR-4573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13602826#comment-13602826 ] Phil John commented on SOLR-4573: - There's a thread on jetty-users that seems to describe this issue: http://dev.eclipse.org/mhonarc/lists/jetty-users/msg02355.html oejh.HttpGenerator:Ignoring extra content when accessing Solr HTTP Admin Console in Solr Cloud example -- Key: SOLR-4573 URL: https://issues.apache.org/jira/browse/SOLR-4573 Project: Solr Issue Type: Bug Components: SolrCloud, web gui Affects Versions: 4.2 Environment: Windows x64 java version 1.7.0_11 Java(TM) SE Runtime Environment (build 1.7.0_11-b21) Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode) Reporter: Phil John Priority: Minor When running the example config included in the Solr distribution based on the instructions here: http://wiki.apache.org/solr/SolrCloud#Example_A:_Simple_two_shard_cluster Any requests to pages in the web gui cause a warning log message to be raised on Jetty's STDOUT 2013-03-13 19:52:45.827:WARN:oejh.HttpGenerator:Ignoring extra content followed by the content of the file being served. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-4573) oejh.HttpGenerator:Ignoring extra content when accessing Solr HTTP Admin Console in Solr Cloud example
Phil John created SOLR-4573: --- Summary: oejh.HttpGenerator:Ignoring extra content when accessing Solr HTTP Admin Console in Solr Cloud example Key: SOLR-4573 URL: https://issues.apache.org/jira/browse/SOLR-4573 Project: Solr Issue Type: Bug Components: SolrCloud, web gui Affects Versions: 4.2 Environment: Windows x64 java version 1.7.0_11 Java(TM) SE Runtime Environment (build 1.7.0_11-b21) Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode) Reporter: Phil John Priority: Minor When running the example config included in the Solr distribution based on the instructions here: http://wiki.apache.org/solr/SolrCloud#Example_A:_Simple_two_shard_cluster Any requests to pages in the web gui cause a warning log message to be raised on Jetty's STDOUT 2013-03-13 19:52:45.827:WARN:oejh.HttpGenerator:Ignoring extra content followed by the content of the file being served. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
