lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shai Erera (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-5536) TaxonomyFacetSumInt/FloatAssociations should not rollup()
Date Tue, 18 Mar 2014 15:21:43 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shai Erera updated LUCENE-5536:
-------------------------------

    Attachment: LUCENE-5536.patch

Patch removes the call to rollup(). I checked and the rest is not a problem today:

* We don't allow setting the association dimensions as hierarchical
* We only encode the exact category's ordinal w/ the associated value, and not its parents
* We do add all the category's path components as drill-down terms, which is good. I means
you can associate a document with a/b/c=0.4, and still find this document if a drill-down
on a/ is made

So all in all it was just the rollup() call that had to be removed. I plan to commit this
shortly.

> TaxonomyFacetSumInt/FloatAssociations should not rollup()
> ---------------------------------------------------------
>
>                 Key: LUCENE-5536
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5536
>             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
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message