lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomás Fernández Löbbe (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SOLR-7795) Fold Interval Faceting into Range Faceting
Date Fri, 07 Aug 2015 22:32:45 GMT

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

Tomás Fernández Löbbe commented on SOLR-7795:
---------------------------------------------

Thanks [~liahsuan], could you update the pull request?
Skimmed at your commits, I really like how the SolrJ looks like. The one problem I see, is
that in the xml/json response, the key is repeated when faceting on the same field, like:

{code}...facet.range=price&facet.range.start=0&facet.range.end=50&facet.range.gap=10&f.price.facet.range.set=[50,*]&wt=json
{code}
will generate something like:

{code}
"facet_counts":{
    "facet_queries":{},
    "facet_fields":{},
    "facet_dates":{},
    "facet_ranges":{
      "price":{
        "counts":[
          "0.0",3,
          "10.0",2,
          "20.0",0,
          "30.0",0,
          "40.0", 0],
        "gap":10.0,
        "start":0.0,
        "end":50.0},
      "price":{
        "counts":{
          "[50,*]":3}}},
    "facet_intervals":{},
    "facet_heatmaps":{}}
{code}

Would it be possible to integrate the two "price" elements? I guess that means that for intervals
we can't use "counts" for intervals.

> 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


Mime
View raw message