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

Make pipeline version scoped at organism level rather than global #1728

Open
chaoran-chen opened this issue May 1, 2024 · 0 comments · May be fixed by #3534
Open

Make pipeline version scoped at organism level rather than global #1728

chaoran-chen opened this issue May 1, 2024 · 0 comments · May be fixed by #3534
Assignees
Labels
backend related to the loculus backend component feature Feature proposal v1.0 Tasks that are crucial for a Loculus 1.0 release

Comments

@chaoran-chen
Copy link
Member

chaoran-chen commented May 1, 2024

As a maintainer, I want to be able to update the processing pipeline of a single organism at a time without bumping versions of the pipelines of other organisms (which then also leads to the reprocessing of data of the other organisms).

At the moment, the backend maintains a single processing pipeline version and only accepts data that have the current version or a higher version. This is maintained across all organisms. I.e., if we want to upgrade the pipeline for one organism, we have to upgrade the pipelines for all other organisms as well.

This should be changed. We should be able to have pipelines with different version numbers for different organisms. I think that we would add an organism column to the current_processing_pipeline.

@chaoran-chen chaoran-chen added the backend related to the loculus backend component label May 1, 2024
@chaoran-chen chaoran-chen added this to the post-MVP milestone May 1, 2024
@chaoran-chen chaoran-chen moved this to Backlog in Planning May 1, 2024
@chaoran-chen chaoran-chen added the feature Feature proposal label Sep 1, 2024
@chaoran-chen chaoran-chen modified the milestones: post-MVP, Release v1.0 Sep 15, 2024
@chaoran-chen chaoran-chen added the v1.0 Tasks that are crucial for a Loculus 1.0 release label Oct 1, 2024
@chaoran-chen chaoran-chen removed this from the Release v1.0 milestone Oct 1, 2024
@fhennig fhennig linked a pull request Jan 16, 2025 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend related to the loculus backend component feature Feature proposal v1.0 Tasks that are crucial for a Loculus 1.0 release
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

2 participants