You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Zack Liang (JIRA)" <ji...@apache.org> on 2015/08/05 06:45:04 UTC

[jira] [Commented] (SOLR-7795) Fold Interval Faceting into Range Faceting

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

Zack Liang commented on SOLR-7795:
----------------------------------

Hi [~tomasflobbe], the patch has been updated according to your feedback.

It can support multiple range facet in a single request now. I added a test case "testSolrJWithMultipleRangeFacets()" to check this in TestIntervalFaceting.

For the syntax, the response will be included in the list of "RangeFacet". I created a inner class "Interval" within RangeFacet to hold the response. The method "addIntervalRangeFacet" remains the same for consistency with "addNumericRangeFacet" and "addDateRangeFacet" methods in the range facet family.

Please let me know your thoughts, thanks!

> Fold Interval Faceting into Range Faceting
> ------------------------------------------
>
>                 Key: SOLR-7795
>                 URL: https://issues.apache.org/jira/browse/SOLR-7795
>             Project: Solr
>          Issue Type: Task
>            Reporter: Tomás Fernández Löbbe
>             Fix For: 5.3, Trunk
>
>
> Now that range faceting supports a "filter" and a "dv" method, and that interval faceting is supported on fields with {{docValues=false}}, I think we should make it so that interval faceting is just a different way of specifying ranges in range faceting, allowing users to indicate specific ranges.
> I propose we use the same syntax for intervals, but under the "range" parameter family:
> {noformat}
> facet.range=price&
> f.price.facet.range.set=[0,10]&
> f.price.facet.range.set=(10,100]
> {noformat}
> The counts for those ranges would come in the response also inside of the "range_facets" section. I'm not sure if it's better to include the ranges in the "counts" section, or in a different section (intervals?sets?buckets?). I'm open to suggestions. 
> {code}
> "facet_ranges":{
>       "price":{
>         "counts":[
>           "[0,10]",3,
>           "(10,100]",2]
>        }
> }
> {code}
> or…
> {code}
> "facet_ranges":{
>       "price":{
>         "intervals":[
>           "[0,10]",3,
>           "(10,100]",2]
>        }
> }
> {code}
> We should support people specifying both things on the same field.
> Once this is done, "interval faceting" could be deprecated, as all it's functionality is now possible through range queries. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org