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.
On 7/17/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: > ...but i don't understand why both checking isTokenized() ...
shouldn't
On 7/16/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: > ...but i don't understand why both checking isTokenized() ... shouldn't
: > multiValued() be enough?
:
: A field could return "false" for multiValued() and still have multiple
: tokens per document for that field.
ah .. right ... sorry:
: > ...but i don't understand why both checking isTokenized() ... shouldn't
: > multiValued() be enough?
:
: A field could return "false" for multiValued() and still have multiple
: tokens per document for that field.
ah .. right ... sorry: multiValued() indicates wether multiple discreet
values
On 7/16/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: There is currently no way to force Solr to use the FieldCache method.
I'm having a hard time remembering why this is ... i see the line in
SimpleFacets that says...
if (sf.multiValued() || ft.isTokenized() || ft instanceof BoolField) {
: There is currently no way to force Solr to use the FieldCache method.
I'm having a hard time remembering why this is ... i see the line in
SimpleFacets that says...
if (sf.multiValued() || ft.isTokenized() || ft instanceof BoolField) {
// Always use filters for booleans... we know the
I've tried both of your recommendations (use facet.enum.cache.minDf=1000 and
optimise the index). The query time is around 0.4-0.5s now but it's still
slow compared to the old "string" type. I haven't tried to increase
filterCache but 100 of cached items looks a bit too much for my server
atm.
On 7/16/07, climbingrose <[EMAIL PROTECTED]> wrote:
Thanks Yonik. In my case, there is only one "title" field per document so is
there a way to force Solr to work the old way? My analyser doesn't break up
the "title" field into multiple tokens. It only tries to format the field
value (to lower ca
Thanks Yonik. In my case, there is only one "title" field per document so is
there a way to force Solr to work the old way? My analyser doesn't break up
the "title" field into multiple tokens. It only tries to format the field
value (to lower case, remove unwanted chars and words). Therefore, it's
Since you went from a non multi-valued "string" type (which Solr knows
has at most one value per document) to a custom analyzer type (which
could produce multiple tokens per document), Solr switched tactics
from using the FieldCache for faceting to using the filterCache.
Right now, you could try
Hi all,
My facet browsing performance has been decent on my system until I add my
custom Analyser. Initially, I facetted "title" field which is of default
string type (no analysers, tokenisers...) and got quick responses (first
query is just under 1s, subsequent queries are < 0.1s). I created a c
10 matches
Mail list logo
