Maximum length for a facet category parameter?

Developers Search Interface
1

I have a long title for a facet category but it seems to be ignoring the last 4 characters of the category name, this is a problem as there are 2 categories that have the same name and are differentiated by a 4 digit code at the end, so both are displayed on the results page.

the character length is 48 characters long including the ‘+’ for spaces
when experimenting the last 4 characters are ignored and when removed the search still works

2

I’m unaware of any documented limits in the lengths of these values so I will raise a ticket with the developers.

Could you please let me know what version of Funnelback you are using as faceted navigation has undergone a number of changes in recent versions.

3

We’re on 15:10.0 in produciton

4

Ticket has been raised

5

Hi
I think one of these limits might be causing you trouble:

  • In the indexer:
    -SORTSIG<num> - How many [UTF-8] characters in a word are significant. Default 20.
    If any single word in the facet category is longer than that you will need to increase that value in the indexer options: indexer_options=-SORTSIG50. Note that after setting this you will need to re-index the live view or run an update.
  • In the query processor:
    -phrase_prox_word_limit=<I> - Phrase or proximity terms with more than this number of words will be shortened by deleting words from the right. E.g. If this limit were 4 thento be or not
    to bewould be processed asto be or not (range 1 - unlimited) [Not CGI]
    Try setting that to a higher value e.g. 20 (default is either 7 or 12 depending on the version). This is set in the query processor options: query_processor_options=-phrase_prox_word_limit=20.
6

Hi Luke
Thanks for this - have tried increasing the SORTSIG and added the word limit and still getting the same problem
It is a document collection (PDFs mainly with custom metadata fields) - would this make any difference?

7

Probably not, what does your metadata look like?

8

Hi Luke
I realised I was setting the config on the wrong collection! This is working now -(needed to go on the meta collection).

Many thanks

9

haha at least it is solved now :slight_smile:

how long was it?

10

Set these
SORTSIG50 and -phrase_prox_word_limit set to 30

Amazing what a week’s holiday does!