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

genetable version added to info api #11290

Open
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

rajeswari2904
Copy link

@rajeswari2904 rajeswari2904 commented Dec 16, 2024

Fix #10299

  • Genetable version added to info api response and model class,maven properties file.
  • Genetable version added to info table in cgds.sql and migration.sql scripts.
  • Genetable version added to test cases and test properties file.
  • Verified that the info api is returning genetable version in response.
  • Ran all tests to assure nothing else was accidently broken in the java part by running:mvn integration-test.

Copy link
Member

@inodb inodb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks so much @rajeswari2904 ! Made a few comments. The db.version is a bit different from genetable.version - might be good to discuss more if you're still working on this. Feel free to slack me. Thank you!

@@ -31,7 +31,7 @@

<!-- THIS SHOULD BE KEPT IN SYNC TO VERSION IN CGDS.SQL -->
<db.version>2.13.1</db.version>

<genetable.version>hgnc_v2023.10.1</genetable.version>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rajeswari2904 should this be pulled from the SQL instead? Do we need to hardcode it in the pom?

Copy link
Member

@inodb inodb Jan 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the genetable.version is a bit different from db.version

  • the db.version indicates the version of the SQL schema. The backend is only compatible with a specific version of this schema
  • for the genetable version is fine if it differs with the backend code version. No need to hardcode the version in the pom.xml. Whoever loads the gene table data should indicate what version it is

@@ -755,5 +756,5 @@ CREATE TABLE `resource_study` (
);

-- THIS MUST BE KEPT IN SYNC WITH db.version PROPERTY IN pom.xml
INSERT INTO info VALUES ('2.13.1', NULL);
INSERT INTO info VALUES ('2.13.1','hgnc_v2023.10.1', NULL );
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This version should maybe be N/A or empty string. Whoever loads the gene table data should set the version

@@ -1027,4 +1027,6 @@ ALTER TABLE `clinical_event_data` MODIFY COLUMN `VALUE` varchar(3000) NOT NULL;
CREATE INDEX idx_clinical_event_key ON clinical_event_data (`KEY`);
CREATE INDEX idx_clinical_event_value ON clinical_event_data (`VALUE`);
CREATE INDEX idx_sample_stable_id ON sample (`STABLE_ID`);
ALTER TABLE `info` ADD COLUMN `GENE_TABLE_VERSION` varchar(24);
UPDATE `info` SET `GENE_TABLE_VERSION`="hgnc_v2023.10.1";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here also good if the version is empty or N/A

@inodb inodb requested a review from averyniceday January 10, 2025 21:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add gene table version to the api version endpoint?
3 participants