[
https://issues.apache.org/jira/browse/LUCENE-4964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644815#comment-13644815
]
Commit Tag Bot commented on LUCENE-4964:
----------------------------------------
[branch_4x commit] mikemccand
http://svn.apache.org/viewvc?view=revision&revision=1477316
LUCENE-4964: allow custom per-dimension drill-down queries
> Allow custom drill-down sub-queries
> -----------------------------------
>
> Key: LUCENE-4964
> URL: https://issues.apache.org/jira/browse/LUCENE-4964
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/facet
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 5.0, 4.4
>
> Attachments: LUCENE-4964.patch
>
>
> Today the facet module indexes a term for each facet added to a
> document, and DrillDown/SidewaysQuery assume this by creating a
> TermQuery, or OR of TermQuery, for each dimension the app drills down
> on.
> I think we should relax this and allow an [expert] arbitrary query to
> drill down on a given dimension ... e.g., this can enable future
> dynamic faceting methods, or custom app drill-down methods.
> It's easy for DrillDownQuery to do this, but requires generalization
> in DrillSideways, basically just reviving the first approach on
> LUCENE-4748. This approach is somewhat slower, but more general
> ... it will keep using the current method as an optimization when it
> applies.
> This should also fix the possible performance regression from
> LUCENE-4952 when scoreSubDocsAtOnce is true, by using the
> MinShouldMatchSumScorer in that case.
--
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: [email protected]
For additional commands, e-mail: [email protected]
