Hello Akash, This could be achieved by redefining your database transaction calls to log externally in persistent storage a timestamp along with the associated transactions when updates are made to the database. You would then trigger updates to the index based on the specific entries in this log with cron.
Alternatively, you could externally store a checksum of the database once it has been fully indexed, and introduce a conditional statement at startup to only re-update the index when that checksum has been changed. Another possibility would be to store the information on if an entity was already indexed directly in the database itself (possibly with a boolean property). The better choice between these options depends strongly on the peculiarities of your project (choice and size of database, transaction implementations, readily available access to external storage for the logs, etc). On Saturday, December 29, 2018 at 5:02:58 PM UTC-5, Akash Eldo wrote: > > I'm using Firebase Firestore, but I think it has similar callbacks. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/44af403e-4758-4159-b0b1-970183b3b2e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
