Add import aggegation helper

[vish-cs]

Aggregation script is placeholder where the specific import details will be added later.

[gemini-code-assist]

Summary of Changes

Hello @vish-cs, I'm Gemini Code Assist¹! 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 introduces a new BigQuery aggregation helper Cloud Function and seamlessly integrates it into the existing data ingestion workflow. The primary goal is to enhance the data pipeline by adding a dedicated, automated step for performing post-ingestion data aggregation or validation within BigQuery for various imports. This allows for more flexible and specific data processing after the initial dataflow jobs are completed.

Highlights

• New Aggregation Cloud Function: A new Python Cloud Function named aggregation_helper has been introduced. This function is designed to receive a list of imports via an HTTP request and execute specific BigQuery aggregation queries for each import, currently with placeholder logic for 'india_census' and 'us_census'.
• Workflow Integration: The existing spanner-ingestion-workflow.yaml has been updated to incorporate a new run_aggregation step. This step calls the newly deployed aggregation_helper Cloud Function after dataflow jobs are completed, passing the relevant import list for post-ingestion processing.
• Automated Deployment: The cloudbuild.yaml configuration has been modified to include a new step for deploying the import-aggregation-helper Cloud Function. This ensures that the new function is automatically deployed as part of the CI/CD pipeline, with necessary environment variables like BQ_DATASET_ID configured.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces a new Cloud Function, aggregation-helper, designed to run post-import aggregation queries in BigQuery. The function is integrated into the existing spanner-ingestion-workflow. The changes also include updating the Cloud Build configuration to deploy this new function and modifying the workflow YAML to invoke it.

My review has identified a critical issue in the new Cloud Function related to SQL syntax that will cause it to fail. I've also included several suggestions to improve code quality, maintainability, and configuration hygiene.

[n-h-diaz]

Thanks for adding this! We can update with specifics for each import once it's in