You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shai Erera (JIRA)" <ji...@apache.org> on 2013/02/12 13:01:16 UTC
[jira] [Resolved] (LUCENE-4772) Move Facet associations to new
FacetsAggregator API
[ https://issues.apache.org/jira/browse/LUCENE-4772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shai Erera resolved LUCENE-4772.
--------------------------------
Resolution: Fixed
Fix Version/s: 5.0
4.2
Committed to trunk and 4x.
> Move Facet associations to new FacetsAggregator API
> ---------------------------------------------------
>
> Key: LUCENE-4772
> URL: https://issues.apache.org/jira/browse/LUCENE-4772
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/facet
> Reporter: Shai Erera
> Assignee: Shai Erera
> Fix For: 4.2, 5.0
>
> Attachments: LUCENE-4772.patch
>
>
> Move facets associations to the new bulk FacetsAggregator API. Also, today when you index categories with associations, the categories are written to two fields redundantly - the associations field and the counting list field. However, when you aggregate them, you only need to read the associations field. The counting list field is redundant here.
> If an app requires indexing the categories into two lists, it can do so by adding the categories w/ associations using AssociationFacetFields and the plain categories (w/ their hierarchy etc.) using FacetFields.
> I will post a patch shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org