Handling Orphaned Records in Firebase Extension with Typesense
TLDR David raised a concern about Typesense records not being deleted when parent collections are removed. Jason confirmed that Firestore does not trigger delete events for individual documents when parent collections are dropped.
Jun 28, 2023 (3 months ago)
• I'm using the firebase extension with a forked cloud function to index records from firestore to typesense
• I'm monitoring a nested firebase sub-collection with the path
• In some of our tests, we prop up test collections, add values, and tear down by removing
• After removing the parent
collection1typesense records from
collection3are not being deleted, and they're building up very quickly in our dev cluster
I read somewhere that this may require another firebase cloud function that removes orphaned records from typesense when one of their parent collections is deleted from firestore. Is this the correct approach?
Indexed 2776 threads (79% resolved)
Discussion on Firebase Extension for Typesense
Jason announced the release of a Firebase Extension for Typesense, leading to a discussion with Gabe about capabilities and scalability concerns. Other users, John and A, simply expressed their admiration.
Handling Order of Firestore Events for Synchronization with Typesense.
Ross ran into an issue with Firestore events triggering out of order, causing synchronization inconsistency between Firestore and Typesense. With advice and input from Jason and Kishore Nallan, they implemented a debouncing solution using redis, ensuring that the latest Firestore data is synced to Typesense accurately.
Configuring Typesense Extension for Nested Fields in Firebase Collection
David had issues indexing nested fields using the Typesense extension. Jason offered advice on specifying schemas and prioritizing specific fields, but there remained unresolved challenges with the schema.