Skip to content

Conversation

@brfrn169
Copy link
Collaborator

@brfrn169 brfrn169 commented Nov 23, 2025

Description

Previously, when a virtual table did not exist, VirtualTableInfoManager returned null without caching the result. This caused repeated queries to the storage admin for non-existent virtual tables, leading to unnecessary overhead. By implementing negative caching, we can avoid these redundant lookups.

Related issues and/or PRs

N/A

Changes made

  • Enabled negative caching in VirtualTableInfoManager to cache non-existent virtual table lookups
  • Updated corresponding test to verify negative caching behavior

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

  • I have commented my code, particularly in hard-to-understand areas.
  • I have updated the documentation to reflect the changes.
  • I have considered whether similar issues could occur in other products, components, or modules if this PR is for bug fixes.
  • Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
  • Tests (unit, integration, etc.) have been added for the changes.
  • My changes generate no new warnings.
  • Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

N/A

Release notes

N/A

@brfrn169 brfrn169 self-assigned this Nov 23, 2025
Copilot AI review requested due to automatic review settings November 23, 2025 06:55
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @brfrn169, 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 introduces negative caching to the VirtualTableInfoManager to enhance performance. By caching the absence of virtual table information, the system avoids redundant calls to the storage admin for non-existent tables, thereby reducing overhead and improving efficiency in scenarios where virtual tables are frequently queried but not found.

Highlights

  • Negative Caching: Enabled negative caching in VirtualTableInfoManager to store the absence of virtual table information, preventing repeated queries for non-existent tables.
  • Cache Type Update: The virtualTableInfoCache now stores Optional<VirtualTableInfo> instead of VirtualTableInfo directly, allowing it to cache Optional.empty() for non-existent entries.
  • Performance Improvement: This change significantly reduces unnecessary overhead by avoiding redundant lookups to the storage admin for virtual tables that do not exist.
  • Test Case Update: An existing test case was updated to verify that the admin.getVirtualTableInfo method is called only once for a non-existent virtual table after the negative caching implementation.
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.

Copy link
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 introduces negative caching to VirtualTableInfoManager to improve performance by caching lookups for non-existent virtual tables. The implementation correctly uses Optional<VirtualTableInfo> in the LoadingCache to store both successful lookups and negative results. The corresponding tests are also updated to verify the new caching behavior. The change is logical and well-executed. I have one suggestion regarding cache configuration to enhance robustness against potential memory issues.

Copilot finished reviewing on behalf of brfrn169 November 23, 2025 06:57
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR implements negative caching in VirtualTableInfoManager to improve performance by caching non-existent virtual table lookups. Previously, when a virtual table did not exist, the manager would return null without caching, causing repeated queries to the storage admin. The implementation wraps the cache value type in Optional to distinguish between "not yet cached" and "cached as non-existent".

Key changes:

  • Changed cache type from LoadingCache<TableKey, VirtualTableInfo> to LoadingCache<TableKey, Optional<VirtualTableInfo>> to enable negative caching
  • Updated cache loader to return Optional directly instead of unwrapping with orElse(null)
  • Modified getVirtualTableInfo to unwrap the cached Optional value with orElse(null) to maintain API compatibility

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
VirtualTableInfoManager.java Changed cache type to use Optional wrapper and updated cache loader and retrieval logic to support negative caching
VirtualTableInfoManagerTest.java Updated test name and assertions to verify that non-existent virtual tables are cached (1 admin call instead of 3)

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@brfrn169 brfrn169 force-pushed the enable-negative-cache-for-virtual-table-metadata branch from 0514661 to c24b16d Compare November 23, 2025 12:03
Copy link
Contributor

@feeblefakie feeblefakie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you!

Copy link
Contributor

@komamitsu komamitsu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

Copy link
Contributor

@Torch3333 Torch3333 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

@brfrn169 brfrn169 merged commit 709b5a7 into master Nov 25, 2025
339 of 344 checks passed
@brfrn169 brfrn169 deleted the enable-negative-cache-for-virtual-table-metadata branch November 25, 2025 02:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants