[
https://issues.apache.org/jira/browse/SOLR-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994661#comment-12994661
]
David Smiley commented on SOLR-1240:
------------------------------------
Two comments:
1. I think we should let it be known that "facet.date" is deprecated in 3.1.
That way it can be removed in a future release without waiting yet another
release.
2. I think it's very odd that the default for the include parameter is for both
edges to be inclusive. This means double-counting! Yes, that's how it used to
work, but I argue it never should have worked that way and I don't think anyone
is actually depending on this behavior. So backwards-compatibility is moot. I
propose "lower" be the default.
> 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]
