Cache on Typesense and "amount" Field Issue
TLDR Max encountered a facet field error regarding the "amount" field. Kishore Nallan and James suggested checking the search query and setting "amount" as a facet: true in the schema.
Feb 06, 2023 (7 months ago)
Max
01:31 PMIs there something like a cache on Typesense?
I swapped my index and I'm getting
Unhandled Rejection (Error): 404 - Could not find a facet field named `amount` in the schema.Double checked all the code - there is no reference to amount anywhere else š¤·āāļø
Max
01:32 PM 22 | try {
23 | typesenseResponse = await this._adaptAndPerformTypesenseRequest(instantsearchRequests);
24 |
> 25 | const adaptedResponses = typesenseResponse.results.map((typesenseResult, index) => {
| ^ 26 | this._validateTypesenseResult(typesenseResult);
27 | const responseAdapter = new SearchResponseAdapter(
28 | typesenseResult,Max
01:33 PMAnd results actually have
amount field š¤
Kishore Nallan
01:59 PM
James
01:59 PMMax
02:00 PMKishore Nallan
02:00 PMMax
02:01 PMfacet_by: "amount"and it's quite possible that collection don't have item with that field.
Checking dashboard now š
Max
02:03 PM
Jason
05:18 PM
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
Faceting issue with Products Collections in Typesense
Carl was unable to facet on a string array. Kishore Nallan and Jason advised ensuring facet counts were being returned and offered to assist in troubleshooting. Issue resolved upon Carl realizing no data was saved in the database.
4Range Filtering and Faceting Discussion
Phil asked about the requirements for range filtering, which Jason explained does not always require faceting. Discussion about different possibilities with Algolia and Typesense ensued, resulting in Phil successfully utilizing the 'Configure' widget.
2Production Typesense Issue with Unexpected Filter Behavior
Ankit flagged a problem with a specific filter on the production server of Typesense. After several exchanges regarding optimisation and version checks, Kishore Nallan provided latest builds to troubleshoot. The filtering within facets issue persists and potential edge cases are being investigated.
5Querying with Typesense-Js and Handling Null Values
michtio was querying using typesense-js and receiving fewer results than expected. Kishore Nallan suggested using different query parameters. Further discussion led to the handling of 'null' values and filtering syntax in the search queries. The thread ended with Jason offering migration support from Algolia to Typesense.
4Typesense Facet Query Issue and Resolution
Stefan wanted to have typesense return count: 0 for filtered out facets, which was not supported. They shared a workaround using a server data call. The solution involved adding "facets: [this.filterConfig.attribute]," for the server adapter to work. Kishore Nallan acknowledged the resolution.