Hey all, could use a confirmation on something: -...
# random
d
Hey all, could use a confirmation on something: • 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
collection1/{wildcard1}/collection2/{wildcard2}/collection3
• In some of our tests, we prop up test collections, add values, and tear down by removing
collection1
• After removing the parent
collection1
typesense records from
collection3
are 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?