-
Notifications
You must be signed in to change notification settings - Fork 837
fix: fix memory_size of sliced string view. #19014
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
a82c847 to
ccabe90
Compare
c894e2c to
caecdd4
Compare
|
@codex review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…)" This reverts commit 8b4a558.
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
before this pr, memory_size rely on total_buffer_len, which is not changed when sliced.
after this pr memory_size is fixed so it only counts for the part it owned. sum of memory_size of a splitted block is eq to the origin memory_size.
if we do need the memory_size of the underly data buffer, we may need a new function or arg.
new impl also consider the size of reading column back from parquet. parquet use a simple bytes array without view.
the buffer of the bytes array is used directly as buffer of view
Tests
Type of change
This change is