[
https://issues.apache.org/jira/browse/SOLR-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882890#comment-13882890
]
Ted Sullivan commented on SOLR-2366:
------------------------------------
Right. I'm following with [~shalinmangar] suggestion to split out your/Hoss's
facet.range.spec / facet.sequence idea as a separate issue. I don't think of
this as extending the gap parameter - I am just providing more explicit
information in the response as to what gaps you actually get (as per your
suggestion of Sept/2011) - similar to what you would get if you implemented
this using facet.query. Looking at the current code, it is pretty easy to add
the range information to the response (right now the response labels are just
the gap starts). This may be user-unfriendly as you say, but I would argue that
it is more friendly than what we have right now - it is certainly more
developer-friendly because it provides better feedback. There is a lot of
interest in this feature (it has been advertised on the SimpleFacetsParameter
Wiki for some time now) as evidenced by earlier comments in this thread. My
original desire was just to make (the patch) usable for those that want to use
it by upgrading Grant's original patch so that it would work with the new(?)
modular class organization. The work required to spiff up the facet.range.gap
response is not large. I haven't impacted the facet.range.spec/buckets approach
but that would seem to require more effort.
> Facet Range Gaps
> ----------------
>
> Key: SOLR-2366
> URL: https://issues.apache.org/jira/browse/SOLR-2366
> Project: Solr
> Issue Type: Improvement
> Reporter: Grant Ingersoll
> Assignee: Shalin Shekhar Mangar
> Priority: Minor
> Fix For: 4.7
>
> Attachments: SOLR-2366.patch, SOLR-2366.patch, SOLR-2366.patch
>
>
> There really is no reason why the range gap for date and numeric faceting
> needs to be evenly spaced. For instance, if and when SOLR-1581 is completed
> and one were doing spatial distance calculations, one could facet by function
> into 3 different sized buckets: walking distance (0-5KM), driving distance
> (5KM-150KM) and everything else (150KM+), for instance. We should be able to
> quantize the results into arbitrarily sized buckets.
> (Original syntax proposal removed, see discussion for concrete syntax)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
