lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gijs Kunze (JIRA)" <>
Subject [jira] Commented: (SOLR-1240) Numerical Range faceting
Date Mon, 26 Jul 2010 09:15:52 GMT


Gijs Kunze commented on SOLR-1240:

bq. p.s. I noticed the start parameter was missing from your xml example, is that on purpose
or a slight oversight?

no ... we've never included "start" in the date faceting (so i didn't include it here) because
it's always the value of the first constraint count ... the only reason "end" was ever included
is because it isn't immediately obvious what the upper bound of the last range is from the
gap: the "hardend" param can modify it.

do you think we really need to explicitly label the start? if we add an optional verbose format
that can obviously include it, is it really needed in this simple output?

Ahh ok, that makes sense. However with the mincount parameter you do not always have the start
parameter, nor do you always have both values of a single count. This not be much of an issue
with dates and integers as you can simply add the gap to the start value but with floating
point numbers I'm a little more wary adding the gap to floating point values due to rounding

The verbose response option was just a thought. While some parts might be useful thinking
more about it the filter response isn't as useful as I thought it would be while writing the
post. It's just that I'd like it if there were more of a link between the facets one selects
and the filters based on those facets. But I guess that's another discussion.

> Numerical Range faceting
> ------------------------
>                 Key: SOLR-1240
>                 URL:
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>            Reporter: Gijs Kunze
>            Priority: Minor
>         Attachments: SOLR-1240.patch, SOLR-1240.patch, SOLR-1240.patch, SOLR-1240.patch,
SOLR-1240.patch, SOLR-1240.patch, SOLR-1240.patch, SOLR-1240.patch
> For faceting numerical ranges using many facet.query query arguments leads to unmanageably
large queries as the fields you facet over increase. Adding the same faceting parameter for
numbers which already exists for dates should fix this.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

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

View raw message