Post processing on two fields means you might have to implement your own
pagination too instead of using facet.limit and facet.offset. Potentially
over millions of usernames. It also renders facet.mincount useless.
Thomas
Op wo 4 jan. 2023 om 18:59 schreef Mikhail Khludnev :
> Hello Julia,
> I'm
Hello Julia,
I'm not sure why not just post process facet values of two fields. Overall,
JSON Facets are not extendable (btw, why?). To hack them you need to extend
FacetModule and inject your custom facet processor somewhere
around
org.apache.solr.search.facet.FacetParser#parseFacetOrStat(java.la
Hi Julia,
As I'm working with indexes that are updated infrequently and queried very
frequently, I would duplicate that data with copyField directives at index
time. Writing a custom facet processor comes with the risk that it might
break with a Solr upgrade.
Are you talking millions of unique us
Hi everyone,
We have two multi-valued fields, both containing usernames, and we'd like to
compute the combined counts across both fields. For example, if we were to
facet on these two docs:
doc1: { field1: [user1, user2], field2: [user3, user4] }
doc2: { field1: [user1, user3], field2: [user2]
