lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Muldowney (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-2894) Implement distributed pivot faceting
Date Fri, 15 Feb 2013 21:23:14 GMT

    [ https://issues.apache.org/jira/browse/SOLR-2894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579505#comment-13579505
] 

Andrew Muldowney edited comment on SOLR-2894 at 2/15/13 9:21 PM:
-----------------------------------------------------------------

As Chris said above me I've been working on distributed pivot faceting. The model had to be
reworked to support this change. The new workflow is each shards result goes into a shardRequest
map, those maps are combined and converted into a list what is what is is looked at. The combined
results are compared to each shard's and refinement requests are made. Once all the refinement
requests are made another round of refinement is queued up, this time going one level deeper
than the previous refinement requests. Because of the nature of the system distributedprocess(rb)
needed to be called from the refinepivotfacets to actually take the enqueued refinement requests
and make them into fully fledged refinement queries. This caused some issue where other refinment
types would get recalled as their refinement identifier was never cleared, Field facets are
slightly modified to have a boolean for "needsRefinements" and one for "wasRefined" to help
distinguish.
                
      was (Author: andrew.muldowney):
    As Chris said above me I've been working on distributed pivot faceting. The model had
to be reworked to support this change. The new workflow is each shards result goes into a
shardRequest map, those maps are combined and converted into a list what is what is is looked
at. The combined results are compared to each shard's and refinement requests are made. Once
all the refinement requests are made another round of refinement is queued up, this time going
one level deeper than the previous refinement requests. Because of the nature of the system
distributedprocess(rb) needed to be called from the refinepivotfacets to actually take the
enqueued refinement requests and make them into fully fledged refinement queries. This caused
some issue where other refinment types would get recalled at their refinement identifier was
never cleared, Field facets are slightly modified to have a boolean for "needsRefinements"
and one for "wasRefined" to help distinguish.
                  
> Implement distributed pivot faceting
> ------------------------------------
>
>                 Key: SOLR-2894
>                 URL: https://issues.apache.org/jira/browse/SOLR-2894
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Erik Hatcher
>             Fix For: 4.2, 5.0
>
>         Attachments: SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch,
SOLR-2894.patch, SOLR-2894.patch, SOLR-2894.patch, SOLR-2894-reworked.patch
>
>
> Following up on SOLR-792, pivot faceting currently only supports undistributed mode.
 Distributed pivot faceting needs to be implemented.

--
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message