lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] [Commented] (LUCENE-5536) TaxonomyFacetSumInt/FloatAssociations should not rollup()
Date Tue, 18 Mar 2014 15:23:45 GMT


Michael McCandless commented on LUCENE-5536:


> TaxonomyFacetSumInt/FloatAssociations should not rollup()
> ---------------------------------------------------------
>                 Key: LUCENE-5536
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/facet
>            Reporter: Shai Erera
>         Attachments: LUCENE-5536.patch
> Stumbled upon this by accident when I reviewed the code. The previous associations impl
never rolled-up. The assumption is that association values are given to exact categories and
have no hierarchical meaning. For instance if a document is associated with two categories:
{{Category/CS/Algo}} and {{Category/CS/DataStructure}} with weights {{0.95}} and {{0.43}}
respectively, it is not associated with {{Category/CS}} with weight {{1.38}}! :)
> If the app wants to association values to apply to parents in the hierarchy as well,
it needs to explicitly specify that (as in passing the hierarchy categories with their own
association value).
> I will fix the bug and also make sure the app cannot trip it by accidentally specifying
hierarchical on these categories, or that if it does (cause e.g. it indexes the categories
for both counting and assoc values) then we don't apply the association to all the categories
in the hierarchy.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message