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

Toke Eskildsen commented on SOLR-7296:
--------------------------------------

Shai: For me the main concern is not the sidecar part, but the central part. I 
am thinking about distributed search here. Is Lucene faceting with taxonomy 
index capable of merging facet results across installations (needed for 
SolrCloud) and if so, do they each have their own independent taxonomy indexes 
or do they need to share a single one?

As for hierarchical faceting, then Solr currently does not have real support 
for that. Being the author of LUCENE-2369 & SOLR-2412 I would like to see it 
happen, both for Solr and Lucene DV. That is for another JIRA, so I'll just add 
that the technique I used was to have an auxiliary structure with a numeric 
entry for each ordinal, which was calculated from a single pass through all 
paths.

> Reconcile facetting 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]

Reply via email to