[
https://issues.apache.org/jira/browse/SOLR-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-397:
--------------------------
Attachment: SOLR-397.patch
Spurred on by recent email threads about this, i sat down and got the
previously mentioned design working (with tests!)
this patch implements the "facet.date.include" param mentioned about with the
specified semantics. the only change is that i discovered
facet.date.other=before and facet.date.other=after don't currently included the
start/end (respectively) range boundaries ... so i made the default for
facet.date.include be [lower,upper,edge] for back compatibility.
I think this approach makes more sense then the proposal in SOLR-1402 because
these semantics make it easy to always get a series of ranges (including the
before/after ranges) that are "adjacent" w/o overlapping (using either [lower],
[lower,edge], [upper], or [upper,edge])
> options for dealing with range endpoints in date facets
> -------------------------------------------------------
>
> Key: SOLR-397
> URL: https://issues.apache.org/jira/browse/SOLR-397
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Attachments: SOLR-397.patch
>
>
> Date faceting should support configuration for controlling how edge
> boundaries are dealt with.
--
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: [email protected]
For additional commands, e-mail: [email protected]
