[jira] Resolved: (SOLR-316) add param to force either termenum or fieldcache in SimpleFacets

["Hoss Man (JIRA)" <ji...@apache.org>]

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

Hoss Man resolved SOLR-316.
---------------------------

       Resolution: Fixed
    Fix Version/s: 1.4
         Assignee: Yonik Seeley

yep.

as a result of Yonik's work, we now have a facet.method param

> add param to force either termenum or fieldcache in SimpleFacets
> ----------------------------------------------------------------
>
>                 Key: SOLR-316
>                 URL: https://issues.apache.org/jira/browse/SOLR-316
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>            Assignee: Yonik Seeley
>            Priority: Minor
>             Fix For: 1.4
>
>
> from this thread...
> http://www.nabble.com/Slow-facet-with-custom-Analyser-tf4087415.html#a11617565
> perhaps we should really have an [f.foo.]facet.field.type=(single|multi)
> param to let clients indicate when they know exactly which method they
> wnat used (getFacetTermEnumCounts vs getFieldCacheCounts) ... if the
> property is not set, the default can be determeined using the
> "sf.multiValued() || ft.isTokenized() || ft instanceof BoolField" logic. 
> ...
> Or a method FieldType.multiToken(), and a new method
> TokenizerFactory/TokenFilterFactory.multiToken() that can be used to
> determine this when the FieldType was created (grrr, too bad they
> weren't abstract classes)
> Or a new attribute in the schema (but I don't like that solution much)
> But allowing the user to select the strategy has some merit, esp since
> there will be an additional way to find the top "n" when I get around
> to finishing my facet-tree-index code. 
> ...
> Thanks for the suggestion Chris. I modified SimpleFacets to check for
> [f.foo.]facet.field.type==(single|multi)
> and the performance has been improved significantly. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.