[
https://issues.apache.org/jira/browse/SOLR-7296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-7296:
-------------------------------
Summary: Reconcile faceting implementations (was: Reconcile facetting
implementations)
I fixed the typo in the title; it was taking me _forever_ to find this issue --
even with http://jirasearch.mikemccandless.com/
I took a deeper look at the new Facet Module (ported from Heliosearch) and I
like it a whole lot! I wish I had done the heatmap faceting stuff there; it
would have saved me some grief. I have more advanced heatmap analytics planned
and I will do it in the Facet module not just because I like the API better but
because I'll need to leverage the analytics there. It mainly needs internal
javadocs. It's important to note that it's both a _framework_ for doing
faceting, and it has some implementations of the various types that plug into
that framework. By comparison, FacetComponent & SimpleFacets has no real
framework and isn't something we should substantially improve going forward,
IMO. In principle, I don't see why Lucene's facet module couldn't be used here
as well as an implementation (ala facet.method=?), plugging into Solr's new
Facet module. I'm not saying it's trivial but my point is that this shouldn't
be an either-or; it's complementary. Let the Facet Module be the framework,
have implementations plug-in, and put the JSON parse & standard/classic request
param parsing a layer above.
I haven't looked at the Analytics Contrib module but it's lack of distributed
support is likely a non-starter, and it's not clear what capabilities lie there
that aren't in the new Facet Module.
> 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
>
> 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
