Skip to content

upgrade embedded cassandra to 5.0.3#3335

Open
derrickaw wants to merge 5 commits intoGoogleCloudPlatform:mainfrom
derrickaw:20260214_embeddedCassandraUpgrade
Open

upgrade embedded cassandra to 5.0.3#3335
derrickaw wants to merge 5 commits intoGoogleCloudPlatform:mainfrom
derrickaw:20260214_embeddedCassandraUpgrade

Conversation

@derrickaw
Copy link
Contributor

@derrickaw derrickaw commented Feb 15, 2026

  1. Upgrade embedded cassandra to 5.0.3.
  2. This requires upgrading commons io and compress.
  3. Fixes build(deps-dev): bump com.github.nosan:embedded-cassandra from 5.0.2 to 5.0.3 #3079.

@derrickaw derrickaw added the improvement Making existing code better label Feb 15, 2026
@gemini-code-assist
Copy link

Summary of Changes

Hello @derrickaw, 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 primarily focuses on updating key dependencies to their latest stable versions. The most significant change involves upgrading the embedded Cassandra instance used for testing, ensuring compatibility and leveraging the latest features or fixes. Additionally, a common utility library has been updated, and an unused test dependency has been removed to streamline the project's build configuration.

Highlights

  • Embedded Cassandra Upgrade: The embedded-cassandra dependency has been upgraded from version 5.0.2 to 5.0.3 in the v2/sourcedb-to-spanner module.
  • Dependency Version Bump: The commons-compress dependency version has been updated from 1.26.2 to 1.28.0.
  • Removed Test Dependency: The metrics-core dependency, previously used in the test scope, has been removed from the v2/sourcedb-to-spanner module.
Changelog
  • pom.xml
    • Updated commons-compress version from 1.26.2 to 1.28.0.
  • v2/sourcedb-to-spanner/pom.xml
    • Upgraded embedded-cassandra version from 5.0.2 to 5.0.3.
    • Removed the metrics-core dependency from the test scope.
    • Added a new comment related to achilles-embedded.
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.

@codecov
Copy link

codecov bot commented Feb 15, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 51.03%. Comparing base (18949a0) to head (d1288a4).

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #3335      +/-   ##
============================================
- Coverage     51.04%   51.03%   -0.01%     
- Complexity     5212     5590     +378     
============================================
  Files           994      994              
  Lines         60672    60672              
  Branches       6651     6651              
============================================
- Hits          30971    30965       -6     
- Misses        27527    27529       +2     
- Partials       2174     2178       +4     
Components Coverage Δ
spanner-templates 70.84% <ø> (-0.03%) ⬇️
spanner-import-export 69.05% <ø> (-0.03%) ⬇️
spanner-live-forward-migration 79.82% <ø> (-0.02%) ⬇️
spanner-live-reverse-replication 77.40% <ø> (-0.06%) ⬇️
spanner-bulk-migration 87.92% <ø> (-0.02%) ⬇️
see 4 files with indirect coverage changes
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@derrickaw derrickaw marked this pull request as ready for review February 15, 2026 20:29
@derrickaw derrickaw requested a review from a team as a code owner February 15, 2026 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improvement Making existing code better size/XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants