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

[WIP][Feature] Support count data size of db and table via /api/show_data #37183

Closed
wants to merge 2 commits into from

Conversation

Jin-H
Copy link
Contributor

@Jin-H Jin-H commented Dec 16, 2023

Why I'm doing:

What I'm doing:

Fixes #34477

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.2
    • 3.1
    • 3.0
    • 2.5

Signed-off-by: redscarf <hongweijin1993@gmail.com>
return dbs.parallelStream()
.mapToLong(this::getDataSizeOfDatabase)
.sum();
}
}
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:
Inconsistent handling of concurrency which might lead to incorrect calculation of data size due to potential concurrent modification of fullNameToDb.

You can modify the code like this:

// Guard fullNameToDb with synchronized block or use a thread-safe approach when iterating over it
synchronized (fullNameToDb) {
    // Access the fullNameToDb map within this block.
}

Secondary concerns that could be addressed but are not as severe include:

  • Potential class cast exceptions if table is not an instance of OlapTable.
  • Inefficiency from parallel streams may not always be beneficial depending on the size of data being processed. It could be counterproductive for small datasets.

Copy link

Quality Gate Passed Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

1 New issue
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

Copy link

[FE Incremental Coverage Report]

pass : 28 / 33 (84.85%)

file detail

path covered_line new_line coverage not_covered_line_detail
🔵 com/starrocks/http/rest/ShowDataAction.java 28 33 84.85% [89, 100, 101, 102, 127]

Copy link

[BE Incremental Coverage Report]

pass : 0 / 0 (0%)

@sduzh sduzh self-requested a review December 20, 2023 01:13
@Jin-H Jin-H changed the title [Feature] Support count data size of db and table via /api/show_data [WIP][Feature] Support count data size of db and table via /api/show_data Jan 17, 2024
Signed-off-by: redscarf <hongweijin1993@gmail.com>
@Jin-H Jin-H requested a review from a team as a code owner February 21, 2024 10:23
@Jin-H Jin-H closed this Feb 21, 2024
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.

/api/show_data automatically aggregates results by db or table
1 participant