CouchDB Document Indexing Issue
TLDR James struggled to index documents from CouchDB, resulting in errors. Kishore Nallan advised checking field definitions and the document's nature. Jason suggested missing "await" statements might cause issues.
Feb 02, 2022 (19 months ago)
James
11:05 AM
Kishore Nallan
11:07 AMJames
11:29 AMKishore Nallan
11:31 AM'default_sorting_field': 'x_top'If you define a default sorting field, that value should always be present in the document. The document you tried to index didn't have this field.
James
11:37 AMKishore Nallan
11:39 AMJames
11:43 AMKishore Nallan
11:44 AMJames
11:49 AMKishore Nallan
11:51 AMdefault_sorting_field configuration and see if it works.James
11:56 AMKishore Nallan
11:57 AMJames
12:02 PMKishore Nallan
12:05 PMJames
12:08 PM
Jason
04:40 PMJason
04:42 PM.get is async, when getting data from couchdbJason
04:44 PM
Typesense
Indexed 2764 threads (79% resolved)
Similar Threads
Sorting Results in Typesense and Handling Errors
Ramees asks about sorting results by distance in Typesense, entering a list of strings as a field, and resolving an error with `fields` format. Kishore Nallan assists with these issues and advises on storing timestamps and proper authentication.
2Querying and Indexing Multiple Elements Issues
Krish queried fields with multiple elements, which Kishore Nallan suggested checking `drop_tokens_threshold`. Krish wished to force OR mode for token, but Kishore Nallan admitted the feature was missing. Krish was able to resolve the issue with url encoding.
Handling Kinesis Stream Event Batching with Typesense
Dui had questions about how to handle Kinesis stream events with Typesense. Kishore Nallan suggested using upsert mode for creation/update and differentiating with logical deletion. After various discussions including identifying and resolving a bug, they finalized to introduce an `emplace` action in Typesense v0.23.
8Troubleshooting 400 Error When Upgrading Typesense Firestore Extension
Orion experienced a `400` error after updating the Typesense Firestore extension, causing issues with cloud functions. They traced the issue back to a data type conflict in their Typesense collection schema after updating. With help from Jason and Kishore Nallan, they resolved the issue by recreating the collection.
5Querying with Not-in in Typesense
Masahiro inquired about using not-in queries in Typesense. Kishore Nallan explained how to conduct such queries by using the "-" operator in the query string, and assisted Masahiro with issues stemming from a high number of exclusion tokens. The problem was eventually resolved by switching to the `multi_search` endpoint.
4