Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Cloud function that updates firestore on delete #31

Open
ivanzvonkov opened this issue Jun 3, 2022 · 2 comments · Fixed by #36
Open

Google Cloud function that updates firestore on delete #31

ivanzvonkov opened this issue Jun 3, 2022 · 2 comments · Fixed by #36

Comments

@ivanzvonkov
Copy link
Contributor

ivanzvonkov commented Jun 3, 2022

Context: Adding an image file to the bucket gs://street2sat-uploaded triggers the street2sat prediction pipeline which adds a new row to the Firestore database with the object detection predictions from that image.

Issue: If an image file is deleted from the bucket gs://street2sat-uploaded the associated row of predictions for that image file remains in the Firestore database. This becomes an issue when image files have been moved (copied then deleted) which results in new duplicate prediction rows in the database.

Potential solution: Create a python Google Cloud function triggered on image file removal that would also remove the associated prediction row from the Firestore database.

@hannah-rae
Copy link
Contributor

Also need to clean existing problems (T1 folder, croptour folder)

@ivanzvonkov ivanzvonkov linked a pull request Aug 5, 2022 that will close this issue
@ivanzvonkov
Copy link
Contributor Author

@hannah-rae do you recall if the existing problems (gs://street2sat-uploaded/2021-07-08-T1, gs://street2sat-uploaded/USA/2021-08-20-croptour) are meant to be removed or just moved to a different folder?

@ivanzvonkov ivanzvonkov reopened this Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants