lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4965) Add dynamic numeric range faceting
Date Mon, 29 Apr 2013 10:30:16 GMT


Michael McCandless updated LUCENE-4965:

    Attachment: LUCENE-4965.patch

New patch, adds generics to make sure the Range instances are the same class, and switches
to simple ctors instead of .newXXXRange.

I also added RangeFRN ... I only use it for the "sub nodes" and not the root node.

I don't think we should try to do the sorting here ... I think that's too simplistic ... we
should do an interval tree (but on a new issue).

Eg the simplistic sorting approach can easily fail to speed things up if, say, most of my
values are > max(range.max) (this will be the case with the Jira search) and you had sorted
"smallest to biggest".
> Add dynamic numeric range faceting
> ----------------------------------
>                 Key: LUCENE-4965
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/facet
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>             Fix For: 5.0, 4.4
>         Attachments: LUCENE-4965.patch, LUCENE-4965.patch, LUCENE-4965.patch, LUCENE-4965.patch,
LUCENE-4965.patch, LUCENE-4965.patch, LUCENE-4965.patch
> The facet module today requires the app to compute the hierarchy
> at index time, eg a timestamp field might use a year/month/day
> hierarchy.
> While this gives great performance, since it minimizes the search-time
> computation, sometimes it's unfortunately useful/necessary to do things entirely at
> search time, like Solr does.
> E.g. I'm playing with a prototype Lucene search for Jira issues
> and I'd like to add a drill down+sideways for "Updated in past day,
> 2 days, week, month" etc.  But because time is constantly advancing,
> doing this at index time is a not easy ...

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