[
https://issues.apache.org/jira/browse/SOLR-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-2383:
------------------------------
Attachment: SOLR-2383.patch
Yonik, you're right. With the new default to have the upper range exclusive, we
need to adjust the fq.
This new patch uses '}' as upper boundary for the filters for both range and
date, making the counts correct for the example.
NOTE: I have not attempted to make it smart enough to obey facet.range.include.
> Velocity: Generalize range and date facet display
> -------------------------------------------------
>
> Key: SOLR-2383
> URL: https://issues.apache.org/jira/browse/SOLR-2383
> Project: Solr
> Issue Type: Bug
> Components: Response Writers
> Reporter: Jan Høydahl
> Labels: facet, range, velocity
> Attachments: SOLR-2383.patch, SOLR-2383.patch, SOLR-2383.patch,
> SOLR-2383.patch, SOLR-2383.patch
>
>
> Velocity (/browse) GUI has hardcoded price range facet and a hardcoded
> manufacturedate_dt date facet. Need general solution which work for any
> facet.range and facet.date.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
