Issues with Typesense API Key and Collection Set Up
TLDR Janick had problems with a function after installing an extension. Kishore Nallan clarified the need to create a collection in typesense, providing necessary instructions and resources.
Apr 06, 2022 (17 months ago)
Kishore Nallan10:35 AM
Kishore Nallan10:38 AM
Kishore Nallan10:40 AM
Indexed 2764 threads (79% resolved)
Typesense and Firebase Integration Troubleshooting
Bobby struggled with getting data to Typesense from Firebase. After sharing his logs and settings screenshots, Jason helped him fix the path configuration and suggested ways to successful re-trigger a backfill. This resolved the issue.
Resolving Issues with Firebase Extension and Typesense Configuration
Ernie sought clarification on how to handle the Firebase Extension and typesense collection configuration issues. Jason explained how to correctly specify the path and refresh the page to see updated data. After applying the advice given, Ernie successfully saw the changes.
Troubleshooting 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.
Resolving Issues with Scoped API Keys in Typesense with Golang
Suvarna had problems with generating and using scoped API keys in Typesense with Golang. Several bugs misleading the user were found and fixed by Kishore Nallan.
Resolving Typesense Server Connection with Correct API Keys and Paths
Rubai had trouble creating a working API key for Typesense and understanding number_hits versus num_documents. Jason provided clarification and correct code for generating a search-only API Key and using correct server configurations.