Backport to branch(3) : Add JDBC database permission test (Part 2)

[feeblefakie]

This is an automated backport of the following:

• Original PR: Add JDBC database permission test (Part 2) #2923
• Backported commit: 67b466c

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 JDBC database permission integration tests. The core changes involve improving the robustness of DDL operations in tests, particularly for distributed databases like YugabyteDB, by introducing explicit waits. It also refines user and permission management for specific RDBMS like DB2 within the testing framework, ensuring more comprehensive and reliable permission testing across different database systems.

Highlights

• Refactoring DDL Wait Mechanism: I've refactored the DDL waiting mechanism in integration tests by renaming waitForTableCreation to a more generic waitForDdlCompletion across Cassandra and base permission test classes. This change better reflects that the wait applies to various Data Definition Language operations, not just table creation.
• YugabyteDB DDL Synchronization: I've introduced specific DDL completion waits for YugabyteDB within the JDBC permission integration tests. This addresses potential schema or catalog version mismatch errors by adding a small delay after DDL operations, ensuring consistency in distributed database environments.
• DB2 Permission Handling Enhancements: I've updated the JDBC permission test utilities to conditionally handle user creation and dropping for DB2, skipping these operations where they are not applicable or cause issues. Additionally, I've added specific GRANT statements for DB2 to ensure proper permission testing for that RDBMS.
• Table Metadata Adjustment: I've adjusted the TableMetadata definition in the DistributedStorageAdminPermissionIntegrationTestBase to change the data type of COL_NAME3 from TEXT to INT, which aligns with expected test scenarios.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 or fill out our survey to provide feedback.

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 is a backport that adds JDBC database permission tests, with specific considerations for DB2 and YugabyteDB. The changes involve creating new test classes, updating existing ones to handle different database engines, and modifying base test classes for better DDL operation handling. Overall, the changes are logical and well-structured for extending test coverage. I've identified one high-severity issue related to a potential resource leak in the Cassandra test utilities, which should be addressed.

[KodaiD]

Verified in https://github.com/scalar-labs/scalardb/actions/runs/16740214334.