Richard Scotten
02/16/2026, 1:59 PM{
"created_at": 1770839153,
"default_sorting_field": "createdAt",
"fields": [
{
"facet": false,
"index": true,
"infix": false,
"locale": "",
"name": "sku",
"optional": true,
"sort": false,
"stem": false,
"stem_dictionary": "",
"store": true,
"symbols_to_index": [
"-",
"_"
],
"type": "string"
}
],
"name": "global",
"num_documents": 878462,
"symbols_to_index": [],
"token_separators": []
}
notice I've included the hyphen and underscore for symbols_to_index . Unfortunately, searching for SKUs with three hyphens like N22-9-2SV-1 doesn't work, but I get results if I type the prefix up to N22-9-2 . The only way I've been able to make this work is if I set "facet": true but that seems like a hack. I've read this Typesense Support Article on SKUs, but I don't believe enabling infix or adding the hyphen as a token separator is the move here. Does anybody know how I can get these SKUs indexed?Fanis Tharropoulos
02/16/2026, 2:48 PMsymbols_to_index and hyphen-related queries a bunch since 29.0Richard Scotten
02/16/2026, 6:44 PMquery_by parameter, then it works. If it's not the first, then it doesn't work. See these screenshots for when sku is the first query_by param:Richard Scotten
02/16/2026, 6:45 PMRichard Scotten
02/16/2026, 6:46 PMFanis Tharropoulos
02/17/2026, 2:39 PMRichard Scotten
02/17/2026, 2:39 PMRichard Scotten
02/17/2026, 2:41 PMFanis Tharropoulos
02/17/2026, 2:45 PMFanis Tharropoulos
02/17/2026, 2:47 PMRichard Scotten
02/17/2026, 2:48 PMRichard Scotten
02/17/2026, 2:49 PMRichard Scotten
02/17/2026, 2:51 PMFanis Tharropoulos
02/17/2026, 3:44 PMsymbols_to_index and token_separators are used during the Tokenization process of the query. That's why it works for sku fields and not for idNumberRichard Scotten
02/17/2026, 4:12 PMquery_by field? So if my query is query_by: 'sku, idNumber' then the search query is tokenized using the symbols_to_index defined for sku in my collection config file?Fanis Tharropoulos
02/18/2026, 9:31 AMquery_by field defined, or the one with the most weight in query_by_weights.Richard Scotten
02/18/2026, 1:48 PMRichard Scotten
02/18/2026, 1:52 PMquery_by field according to the symbols_to_index and token_separators of that field.Fanis Tharropoulos
02/18/2026, 3:39 PMRichard Scotten
02/18/2026, 3:41 PMRichard Scotten
02/19/2026, 3:40 AMFanis Tharropoulos
02/19/2026, 9:28 AMRichard Scotten
02/19/2026, 3:01 PMFanis Tharropoulos
02/19/2026, 3:02 PMRichard Scotten
02/19/2026, 3:14 PMRichard Scotten
02/19/2026, 3:18 PMRichard Scotten
03/06/2026, 2:56 PMsymbols_to_index and token_separators are used during the Tokenization process of the query." This is breaking a lot of my searches and is making debugging difficult. Is there an estimation on when this might get fixed?Richard Scotten
03/06/2026, 3:01 PMsymbols_to_index at the field level when the query is tokenized using different token separators. It only works if you query one field at a time, or if all fields have the same token separators and symbols to index. I never had this problem with Algolia or Elasticsearch.Fanis Tharropoulos
03/09/2026, 10:37 AMRichard Scotten
03/10/2026, 8:54 PMRichard Scotten
03/11/2026, 6:40 PMmultiSearch (as you recommended) and it appears the facet_by and max_facet_values params are not being recognized. Is that a bug? I can't find that exception documented in https://typesense.org/docs/30.1/api/federated-multi-search.html or https://typesense.org/docs/30.1/api/search.html#faceting-parameters And if not a bug, how do I get the facets? Do I need to run a third query (regular not multiSearch) to get the facets?Fanis Tharropoulos
03/12/2026, 10:52 AMRichard Scotten
03/12/2026, 5:49 PMRichard Scotten
03/12/2026, 5:50 PMFanis Tharropoulos
03/13/2026, 10:31 AM