Backport to branch(3) : Add more waits for cache expiry

[feeblefakie]

This is an automated backport of the following:

• Original PR: Add more waits for cache expiry #3046
• Backported commit: 693288e

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 backports critical changes aimed at improving the stability and reliability of integration tests. It specifically targets issues related to cache consistency by adding explicit delays before database operations and ensuring that test cases utilize isolated table resources. These modifications help prevent test failures caused by stale cached data or metadata, leading to more robust and predictable test execution.

Highlights

• Integration Test Stability: Introduced a 1-second wait before transactional operations (insert and scan) in integration tests to allow for cache expiry, addressing potential test flakiness.
• Unique Test Table Names: Modified several integration tests to use dynamically generated, unique table names for each test run, preventing interference from stale cache data between tests.
• Refactored Transactional Methods: Updated the transactionalInsert and transactionalScan helper methods in base integration test classes to internally manage DistributedTransactionManager instances, simplifying their usage in test cases.

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 refactors integration tests to improve stability by addressing potential metadata caching issues. The changes introduce waits for cache expiry and use unique table names for tests involving DDL operations, which are excellent strategies for enhancing test isolation and reliability. The refactoring of transactionalInsert and transactionalScan methods to encapsulate transaction management is also a good improvement. I have a few suggestions to further enhance maintainability by reducing code duplication and eliminating magic numbers.