Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BugFix] Before deleting a database, check whether any resource groups are bound #53219

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

blanklin030
Copy link
Contributor

@blanklin030 blanklin030 commented Nov 26, 2024

Why I'm doing:

If delete a database which was bounded to a resource group, the resource group will become invalid. Therefore, we need to check whether a database was bound to a resource group before deleting it

image

What I'm doing:

check whether a database was bound to a resource group before deleting database

Fixes #issue

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.4
    • 3.3
    • 3.2
    • 3.1
    • 3.0

@blanklin030 blanklin030 requested a review from a team as a code owner November 26, 2024 16:15
});

}

public static void checkDbNullAndReport(Database db, String name) {
if (db == null) {
ErrorReport.reportSemanticException(ErrorCode.ERR_BAD_DB_ERROR, name);
Copy link

Choose a reason for hiding this comment

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

The most risky bug in this code is:

Potential null pointer dereference due to `db` being null.

You can modify the code like this:

public static void checkDbExistInResourceGroupAndReport(String dbName) {
    Database db = GlobalStateMgr.getCurrentState().getLocalMetastore().getDb(dbName);
    if (db == null) {
        ErrorReport.reportSemanticException(ErrorCode.ERR_BAD_DB_ERROR, dbName);
        return;
    }
    GlobalStateMgr.getCurrentState().getResourceGroupMgr().getAllResourceGroupNames().forEach(rgName -> {
        GlobalStateMgr.getCurrentState().getResourceGroupMgr().getResourceGroup(rgName).getClassifiers().forEach(classify -> {
            if (classify.getDatabases().contains(db.getId())) {
                ErrorReport.reportSemanticException(ErrorCode.ERR_DROP_DATABASE, dbName, rgName);
            }
        });
    });
}

Copy link

sonarcloud bot commented Nov 26, 2024

Copy link

[Java-Extensions Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[BE Incremental Coverage Report]

pass : 0 / 0 (0%)

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.

1 participant