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

ASF subversion and git services commented on SOLR-12398:
--------------------------------------------------------

Commit aef5a75e1377af41da26dd314b1c0496672d268c in lucene-solr's branch 
refs/heads/branch_7_6 from [~dsmiley]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=aef5a75 ]

SOLR-12398: retroactively add CHANGES.txt back-compat break for 7.5

(cherry picked from commit 2611c22b6b00d73f6ae1fc6996e029f73ee7458d)


> Make JSON Facet API support Heatmap Facet
> -----------------------------------------
>
>                 Key: SOLR-12398
>                 URL: https://issues.apache.org/jira/browse/SOLR-12398
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Facet Module, faceting, JSON Request API, spatial
>            Reporter: Jaime Yap
>            Assignee: David Smiley
>            Priority: Major
>              Labels: heatmap
>             Fix For: 7.5
>
>         Attachments: SOLR-12398.patch, SOLR-12398.patch, 
> repro-facet-heatmaps-response-format-change.patch
>
>
> The JSON query Facet API does not support Heatmap facets. For companies that 
> have standardized around generating queries for the JSON query API, it is a 
> major wart to need to also support falling back to the param encoding API in 
> order to make use of them.
> More importantly however, given it's more natural support for nested 
> subfacets, the JSON Query facet API is be able to compute more interesting 
> Heatmap layers for each facet bucket. Without resorting to the older (and 
> much more awkward) facet pivot syntax.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to