On Thu, Dec 16, 2021 at 5:05 PM Greg Miller <[email protected]> wrote: > > On Thu, Dec 16, 2021 at 1:31 PM Robert Muir <[email protected]> wrote: > > > > On Thu, Dec 16, 2021 at 3:53 PM Greg Miller <[email protected]> wrote: > > > > > > > > TaxonomyReader was recently updated > > > to support bulk ordinal resolution (LUCENE-9476), but SSDV faceting is > > > stuck looking up paths one-at-a-time via SSDV#lookupOrd(ord). This > > > results in a separate TermsEnum#seekExact() call down in > > > Lucene90DocValuesProducer for each ordinal being returned. > > > > > > > I'm confused, where do we do gazillions of lookupOrd(), we should not > > be doing that. The ordinals should be used for all the heavy-duty > > work, and at the very end, only the top-10 or whatever resolved back > > to strings with lookupOrd. Think of it kinda like the stored fields :) > > This is right, but we still need to do the lookup for each value being > returned (which is bounded by the top-n param supplied by the user). > In getAllDims, we'll do "n" lookups for every dimension indexed. So > while we're working in "ordinal space" for doing all the counting and > such, there could still be a somewhat sizable number of ordinals that > need to be looked up after counting. This is where taxo-faceting leans > on bulk lookups.
OK I need to understand this better, because I don't see why it is necessary to do it this way. It definitely is very different from the way solr wiki page documents hierarchical faceting. Maybe we should adopt their approach? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
