Skip to content

fix: cover all possible partitioning configurations with tests and fix a small bug#2699

Merged
cabljac merged 2 commits intonextfrom
fix-partitioning-configs
Mar 25, 2026
Merged

fix: cover all possible partitioning configurations with tests and fix a small bug#2699
cabljac merged 2 commits intonextfrom
fix-partitioning-configs

Conversation

@cabljac
Copy link
Copy Markdown
Contributor

@cabljac cabljac commented Mar 25, 2026

No description provided.

@cabljac
Copy link
Copy Markdown
Contributor Author

cabljac commented Mar 25, 2026

/gemini review

@gemini-code-assist
Copy link
Copy Markdown
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 improves the reliability and correctness of the BigQuery export's partitioning configuration. It resolves a subtle bug in the buildPartitioningConfig function that could lead to improper validation when partitioning was explicitly turned off. Concurrently, the PR introduces a comprehensive set of new unit tests, ensuring that all valid and invalid combinations of partitioning settings are thoroughly tested, thereby enhancing the overall robustness of the partitioning logic and preventing future issues.

Highlights

  • Bug Fix: Corrected a minor bug in the buildPartitioningConfig function where partition-specific fields were incorrectly validated when table partitioning was disabled.
  • Enhanced Test Coverage: Significantly expanded the test suite for buildPartitioningConfig to cover all possible partitioning configurations, including no partitioning, ingestion-time partitioning, timestamp field partitioning, custom field partitioning, and various error conditions.

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

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
Copy Markdown
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

The pull request refactors the buildPartitioningConfig function to improve the handling of partitioning configurations, especially when partitioning is disabled or when dealing with various sentinel values for optional fields. The associated test suite has been significantly expanded and reorganized to cover a wider range of scenarios, including no partitioning, ingestion-time partitioning, timestamp field partitioning, and custom field partitioning, along with more robust error case testing. The reviewer suggests refactoring repetitive test cases using Jest's test.each to enhance test suite conciseness and maintainability.

Copy link
Copy Markdown
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 refactors the tests for buildPartitioningConfig by organizing them into logical describe blocks and expanding test coverage for different partitioning configurations, including no partitioning, ingestion-time, timestamp field, custom field, and error cases. It also includes a minor change to normalize partitioning field values earlier in the buildPartitioningConfig function for improved consistency. A suggestion was made to introduce a helper function in the tests to reduce repetition for cases asserting granularity: "NONE".

@cabljac
Copy link
Copy Markdown
Contributor Author

cabljac commented Mar 25, 2026

/gemini review

Copy link
Copy Markdown
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 refactors the buildPartitioningConfig function's test suite in firestore-bigquery-export/functions/__tests__/config.test.ts to enhance coverage and organization. It introduces new describe blocks for 'no partitioning', 'ingestion-time partitioning', 'timestamp field partitioning', 'custom field partitioning', and 'error cases', covering various scenarios for handling partitioning configurations, including sentinel values and error conditions. Concurrently, the config.ts file was updated by moving the if (!timePartitioning) check to ensure that optional partition field values are normalized before being evaluated, leading to more robust validation logic. There is no feedback to provide.

@cabljac cabljac force-pushed the fix-partitioning-configs branch from 80a3d00 to 83348eb Compare March 25, 2026 17:04
@cabljac cabljac merged commit b6c3f58 into next Mar 25, 2026
7 checks passed
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