lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Commit Tag Bot (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4964) Allow custom drill-down sub-queries
Date Mon, 29 Apr 2013 20:12:16 GMT


Commit Tag Bot commented on LUCENE-4964:

[trunk commit] mikemccand

LUCENE-4964: allow custom per-dimension drill-down queries
> Allow custom drill-down sub-queries
> -----------------------------------
>                 Key: LUCENE-4964
>                 URL:
>             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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message