[
https://issues.apache.org/jira/browse/SOLR-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689773#comment-17689773
]
Jan Høydahl commented on SOLR-7296:
-----------------------------------
Reviving this topic. Much has happended since 2015, and the JSON facet api impl
is mature and ready to rule them all.
In SOLR-13931 we do the first steps for getting rid of Analytics component, so
this ball is rolling!
Wrt classic FacetComponent there was a dev-list thread
(https://lists.apache.org/thread/cnqv6v87w5wbrqcp0cb8scfbyd2q7zl4) a few years
ago that suggested deprecating it, but in a clever way that would keep the
{{facet.field}} API syntax but delegate to JSON facet API through a thin shim.
So I guess that part is up for grabs, and can probably be split into several
smaller steps.
> Reconcile faceting implementations
> ----------------------------------
>
> Key: SOLR-7296
> URL: https://issues.apache.org/jira/browse/SOLR-7296
> Project: Solr
> Issue Type: Task
> Components: faceting
> Reporter: Steve Molloy
> Priority: Major
>
> SOLR-7214 introduced a new way of controlling faceting, the unmbrella
> SOLR-6348 brings a lot of improvements in facet functionality, namely around
> pivots. Both make a lot of sense from a user perspective, but currently have
> completely different implementations. With the analytics components, this
> makes 3 implementation of the same logic, which is bound to behave
> differently as time goes by. We should reconcile all implementations to ease
> maintenance and offer consistent behaviour no matter how parameters are
> passed to the API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
