[
https://issues.apache.org/jira/browse/SOLR-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996236#comment-12996236
]
David Smiley commented on SOLR-1240:
------------------------------------
Of course I totally agree with Yonik. I don't care that much what the default
include is (upper, lower, ...) as long as it doesn't double-count.
Double-counting is bad -- it can lead to a bad user experience. There's
something about "lower" that I feel makes it slightly better than "upper" but I
can't really explain the rationale. I don't think there's any point in
compliance with legacy if nobody depended on the behavior (they couldn't
specify the behavior before either). Just because its easy to set the include,
doesn't mean the default is arbitrary. Any way, if the default remains to
double-count, I'm going to insist that my readers for the second edition of my
book change this value.
> Numerical Range faceting
> ------------------------
>
> Key: SOLR-1240
> URL: https://issues.apache.org/jira/browse/SOLR-1240
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Gijs Kunze
> Assignee: Hoss Man
> Priority: Minor
> Fix For: 3.1, 4.0
>
> 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, SOLR-1240.patch, SOLR-1240.use-nl.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.
-
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]
