[ 
https://issues.apache.org/jira/browse/SOLR-2366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881953#comment-13881953
 ] 

Ted Sullivan commented on SOLR-2366:
------------------------------------

I agree with [~janhoy]'s earlier comment (9/Sep/11):

| One thing this improvement needs to tackle is how to return the range buckets 
in the Response

As is done in facet.query.  Unless we do this, the response is a bit too 
cryptic. I would vote for adding this code before committing it (I'll 
volunteer) and spinning off the facet.range.spec or facet.sequence idea to a 
new issue as Shalin suggests. So for a facet.range.start=0, 
facet.range.end=1000, facet.range.gap=10,90,900 the labels would be as Jan 
suggests: [0 TO 10}, [10 TO 100}, [100 TO 1000}. This would be done even if the 
gaps are constant. As it is now, all you see in the response are the range 
starts rather than the ranges.

> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to