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.

Sign up for GitHub

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

Jump to bottom

Staging database recreation DAG #1989

Closed
AetherUnbound opened this issue May 3, 2023 · 1 comment · Fixed by #2211
Closed

Staging database recreation DAG #1989

AetherUnbound opened this issue May 3, 2023 · 1 comment · Fixed by #2211
Assignees
@AetherUnbound
Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API 🧱 stack: catalog Related to the catalog and Airflow DAGs 🧱 stack: ingestion server Related to the ingestion/data refresh server 🔧 tech: airflow Involves Apache Airflow 🐍 tech: python Involves Python

Comments

@AetherUnbound
Copy link
Collaborator

Description

Create a DAG that matches the one described in #1154: https://docs.openverse.org/projects/proposals/search_relevancy_sandbox/20230406-implementation_plan_update_staging_database.html#dag

Additional context

Part of #392
@AetherUnbound AetherUnbound added 🌟 goal: addition Addition of new feature 🐍 tech: python Involves Python 💻 aspect: code Concerns the software code in the repository 🔧 tech: airflow Involves Apache Airflow 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API 🧱 stack: catalog Related to the catalog and Airflow DAGs 🧱 stack: ingestion server Related to the ingestion/data refresh server labels May 3, 2023
@github-project-automation github-project-automation bot moved this to 📋 Backlog in Openverse Backlog May 3, 2023
This was referenced May 3, 2023
Closed
Closed
@AetherUnbound AetherUnbound self-assigned this May 9, 2023
@AetherUnbound AetherUnbound moved this from 📋 Backlog to 📅 To do in Openverse Backlog May 9, 2023
@AetherUnbound AetherUnbound mentioned this issue May 13, 2023
Merged
8 tasks
This was referenced May 26, 2023
Merged
Open
Merged
@AetherUnbound
Copy link
Collaborator Author

I added a comment on the IP PR about not being able to run the Elasticsearch reindex step. The upshot of this is once #2207 and #2211 are merged, this can be considered done 🙂

@AetherUnbound AetherUnbound linked a pull request Jun 2, 2023 that will close this issue
Deploy staging API after staging DB restore #2211
Merged
8 tasks
@AetherUnbound AetherUnbound mentioned this issue Jun 3, 2023
Merged
8 tasks
@github-project-automation github-project-automation bot moved this from 📅 To do to ✅ Done in Openverse Backlog Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AetherUnbound AetherUnbound

Labels
💻 aspect: code Concerns the software code in the repository 🌟 goal: addition Addition of new feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: api Related to the Django API 🧱 stack: catalog Related to the catalog and Airflow DAGs 🧱 stack: ingestion server Related to the ingestion/data refresh server 🔧 tech: airflow Involves Apache Airflow 🐍 tech: python Involves Python
Projects
Openverse Backlog
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Deploy staging API after staging DB restore WordPress/openverse
1 participant
@AetherUnbound