Backport to branch(3) : Use CoreError for messages of UnsupportedOperationException in Cassandra adapter

[feeblefakie]

This is an automated backport of the following:

• Original PR: Use CoreError for messages of UnsupportedOperationException in Cassandra adapter #3019
• Backported commit: 98ffa4d

Please merge this PR after all checks have passed.

[gemini-code-assist]

Summary of Changes

Hello @feeblefakie, 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 is an automated backport aimed at enhancing the consistency and maintainability of error messages within the Cassandra adapter. It refactors existing UnsupportedOperationException messages, specifically those triggered when the TIMESTAMP data type is encountered, by replacing them with a standardized CoreError enum. This ensures that all related error messages are uniform and centrally managed.

Highlights

• New CoreError Definition: A new CoreError enum entry, CASSANDRA_TIMESTAMP_TYPE_NOT_SUPPORTED, has been introduced to standardize error messages related to the unsupported TIMESTAMP data type in Cassandra.
• Standardized Error Messages: Hardcoded UnsupportedOperationException messages in CassandraAdmin, ResultInterpreter, and ValueBinder classes have been replaced with the newly defined CoreError.CASSANDRA_TIMESTAMP_TYPE_NOT_SUPPORTED.
• Improved Maintainability: This change centralizes error message management, making it easier to maintain and ensure consistency across the Cassandra adapter when dealing with unsupported data types.

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

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 refactors the error handling for the unsupported TIMESTAMP data type in the Cassandra adapter by centralizing the error message in CoreError. This is a good improvement for code maintainability and consistency. The changes correctly replace hardcoded strings in CassandraAdmin, ResultInterpreter, and ValueBinder with the new CoreError enum entry.

While the logic is sound, I'd like to point out that unit tests for the changes in CassandraAdmin seem to be missing. Although ResultInterpreterTest and ValueBinderTest already test for the UnsupportedOperationException, adding similar tests to CassandraAdminTest.java for createTable and addNewColumnToTable would ensure these failure paths are explicitly covered and protected against future regressions.