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] Fix the bug in the persistent index that checks whether page reading is supported. #48659

Merged
merged 2 commits into from
Jul 23, 2024

Conversation

sevev
Copy link
Contributor

@sevev sevev commented Jul 22, 2024

Why I'm doing:

Pindex support read by page in following scenarios:

  1. no compression
  2. compress with page

There are the following scenarios:

  1. upgrade from old version and no compression, the uncompressed_size is 0
  2. generate by new version but disable compression, the uncompressed_size is 0
  3. upgrade from old version and enable shard compression, the uncompressed_size is greater than 0
  4. generate by new version and enable page compression, the uncompressed_size is greater than 0 and each compressed page size is saved in page_off

So when the uncompressed_size is greater than 0, we need to separate shard-compression and page-compression. We will use page_off to judge which compression type is used. So we need to set page_offs as 0 when we upgrade from old version.

What I'm doing:

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

Signed-off-by: sevev <[email protected]>
Signed-off-by: sevev <[email protected]>
@sevev sevev requested a review from a team as a code owner July 22, 2024 04:20
@mergify mergify bot assigned sevev Jul 22, 2024
Copy link

[FE Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[BE Incremental Coverage Report]

pass : 4 / 4 (100.00%)

file detail

path covered_line new_line coverage not_covered_line_detail
🔵 be/src/storage/persistent_index.cpp 4 4 100.00% []

@wyb wyb merged commit cb6ef72 into StarRocks:main Jul 23, 2024
46 checks passed
Copy link

@Mergifyio backport branch-3.3

@github-actions github-actions bot removed the 3.3 label Jul 23, 2024
Copy link

@Mergifyio backport branch-3.2

@github-actions github-actions bot removed the 3.2 label Jul 23, 2024
Copy link

@Mergifyio backport branch-3.1

@github-actions github-actions bot removed the 3.1 label Jul 23, 2024
Copy link
Contributor

mergify bot commented Jul 23, 2024

backport branch-3.3

✅ Backports have been created

Copy link
Contributor

mergify bot commented Jul 23, 2024

backport branch-3.2

✅ Backports have been created

Copy link
Contributor

mergify bot commented Jul 23, 2024

backport branch-3.1

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Jul 23, 2024
… reading is supported. (#48659)

Signed-off-by: sevev <[email protected]>
(cherry picked from commit cb6ef72)
mergify bot pushed a commit that referenced this pull request Jul 23, 2024
… reading is supported. (#48659)

Signed-off-by: sevev <[email protected]>
(cherry picked from commit cb6ef72)
mergify bot pushed a commit that referenced this pull request Jul 23, 2024
… reading is supported. (#48659)

Signed-off-by: sevev <[email protected]>
(cherry picked from commit cb6ef72)
wanpengfei-git pushed a commit that referenced this pull request Jul 23, 2024
… reading is supported. (backport #48659) (#48747)

Co-authored-by: zhangqiang <[email protected]>
wanpengfei-git pushed a commit that referenced this pull request Jul 23, 2024
… reading is supported. (backport #48659) (#48746)

Co-authored-by: zhangqiang <[email protected]>
wanpengfei-git pushed a commit that referenced this pull request Jul 23, 2024
… reading is supported. (backport #48659) (#48745)

Co-authored-by: zhangqiang <[email protected]>
dujijun007 pushed a commit to dujijun007/starrocks that referenced this pull request Jul 29, 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.

3 participants