Skip to content

Remove biomedical tables from deploy/storage/base_bigtable_info.yaml#1807

Open
juliawu wants to merge 1 commit intodatacommonsorg:masterfrom
juliawu:bio-bt-tables
Open

Remove biomedical tables from deploy/storage/base_bigtable_info.yaml#1807
juliawu wants to merge 1 commit intodatacommonsorg:masterfrom
juliawu:bio-bt-tables

Conversation

@juliawu
Copy link
Contributor

@juliawu juliawu commented Mar 11, 2026

As part of removing biomedical data commons from the website repo (it is now being served as its own custom DC), we no longer need the biomedical BT tables in mixer.

This change updates the .yaml configs to stop mixer from reading the biomedical BT tables. This change does not change anything about how those tables get built earlier in the pipeline.

@juliawu juliawu requested review from ajaits and n-h-diaz March 11, 2026 21:03
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request streamlines data configuration by removing references to biomedical Bigtable tables from the base_bigtable_info.yaml file. This change reflects the migration of the biomedical data commons to an independent service, ensuring the mixer component no longer attempts to access these externalized data sources. The modification is purely a configuration update and does not affect the upstream data pipeline.

Highlights

  • Biomedical Data Commons Decoupling: The biomedical data commons has been transitioned to its own custom data commons, making its tables no longer necessary within this repository's configuration.
  • Mixer Configuration Update: The configuration for the mixer component has been updated to remove references to the biomedical Bigtable tables, preventing the mixer from attempting to read them.
Changelog
  • deploy/storage/base_bigtable_info.yaml
    • Removed the biomedical_2026_01_02_03_45_47 entry from the list of tables.
Activity
  • No human activity has been recorded on this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request removes the biomedical BigTable table from the base_bigtable_info.yaml configuration. This change is consistent with the stated goal of separating the biomedical data commons into its own custom Data Commons, which means the main mixer no longer needs to read this table. The change is a straightforward and correct configuration update.

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 this pull request may close these issues.

1 participant