algolia / firestore-algolia-search

Apache License 2.0
112 stars 35 forks source link

Firestore document changes not reflected in algolia index #186

Closed ktan185 closed 11 months ago

ktan185 commented 1 year ago

Good day,

I've currently been using the extension for searching a the title of a video in my videos collection. When I set up the extension, I followed the tutorial found at https://www.youtube.com/watch?v=9BCQHfacqNU and It correctly indexed the current documents in my videos collections into my Algolia index, however whenever I update or add a new document, these changes are not reflected in my algolia index immediately. I have checked the logs for the executeIndexOperation and the function doesn't seem to be invoked either.

smomin commented 11 months ago

hey @ktan185 are you still running into this issue? What version of the integration do you have? Can you provide my the configuration details? Have you used the Admin key to see if it resolves the issue?

ktan185 commented 11 months ago

Hi @smomin, I've just checked, still running into this issue. Currently using the extension on version 1.1.5 (firestore-algolia-search@1.1.5). I've tried to reconfigure the extension with the admin key and still the same result. Heres my algolia index configuration: export-videos-LIMUGMY693-1701379182.json

bleedweedsuz commented 11 months ago

Same thing happed to me. After successfully installed the extension to firebase it copied all the documents to Algolia but after add, update, delete operation in firebase, it does not change anything in Algolia. I watched this tutorial because there is no new updated one. Tutorial 1.

I saw new thing in config like "Database ID" but i am using Firestore. So i just added my collection name as shown in the below image. Or do i have to use (default) here. Screenshot 2023-12-01 at 3 52 18 PM

P.S. i also used admin key it didn't work.

bleedweedsuz commented 11 months ago

Solved: My problem was bad config: in Database ID: (default) <---- for more info

smomin commented 11 months ago

is this issue resolved? If so, can we close it?

ktan185 commented 11 months ago

@bleedweedsuz awesome thanks for this! worked for me too :)

@smomin yes the issue is resolved.