[
https://issues.apache.org/jira/browse/SOLR-13931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689502#comment-17689502
]
Michael Gibney commented on SOLR-13931:
---------------------------------------
[This comment|https://lists.apache.org/thread/jqztlt2pzr27o55k6jvylghg5o6sj5hj]
(from a relevant thread in Jan. 2021) touches on the handful of features in
FacetComponent not yet supported in JSON facets. There aren't many (enough that
even without them it's arguably close enough to parity?). There's also more
discussion in the thread about the general topic of removing FacetComponent --
Jan perhaps that's even what you were thinking of?
{{facet.exists}} and {{facet.field}} terms filter (SOLR-14921) are the only
gaps I'm aware of.
Haha, re: the name, the first thing I say to people who have asked me to
explain JSON facets is: "first of all, it really has nothing to do with JSON"
...
> Decommission Analytics component/handler
> ----------------------------------------
>
> Key: SOLR-13931
> URL: https://issues.apache.org/jira/browse/SOLR-13931
> Project: Solr
> Issue Type: Improvement
> Components: SearchComponents - other
> Reporter: Mikhail Khludnev
> Priority: Major
>
> Spin off from SOLR-13904 discussion.
> let's:
> # Deprecate the analytics component
> # Make a migration path to JSON Facets
> # Make sure that JSON Facets has all of the necessary functionality (median,
> unique, percentile, etc.)
> # Have analytics queries be converted to json facets, and computed that way.
> # Remove the Analytics Component backend
> # Down the road stop supporting analytics component requests all together
> (Make users switch to json facets themselves)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
