Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ensembl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ensembl-gh-mirror
  • ensembl
  • Merge requests
  • !380

Registry: add support for versioned ensembl_metadata DBs [release/97]

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Marek Szuba requested to merge feature/ENSCORESW-3119_rel97 into release/97 Apr 29, 2019
  • Overview 1
  • Commits 1
  • Pipelines 0
  • Changes 1

Created by: mkszuba

Description

Extend the Registry so that it can detect Ensembl metadata databases whose names contain the release number, with backward compatibility with unversioned databases but preference for versioned ones if both forms are present.

Backport of #379 to release/97.

Use case

Since release 96 Ensembl metadata databases have been named ensembl_metadata_XY, where XY is the release number. Unfortunately the Registry has not been updated accordingly so it keeps looking for ensembl_metadata. See ENSCORESW-3119 for additional information.

Benefits

Registry will be able to correctly instantiate MetadataDBAdaptors again.

Possible Drawbacks

A slight increase in computational overhead during Registry initialisation, primarily due to the fact we retain backward compatibility with the old naming convention.

Testing

Have you added/modified unit tests to test the changes?

No.

If so, do the tests pass/fail?

N/A

Have you run the entire test suite and no regression was detected?

Yes, no regression detected.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: feature/ENSCORESW-3119_rel97