-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[fix](cloud) Fix missing privilege to storage vault after restarting FE #40260
[fix](cloud) Fix missing privilege to storage vault after restarting FE #40260
Conversation
The previous implement forgets to build `storageVaultPrivTable` (in-memory) after loading auth information from image, which means the privileges are persisted but unable to use after restarting FE. Note: a new image will be generated after FE restarts.
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
TPC-H: Total hot run time: 38391 ms
|
TPC-DS: Total hot run time: 188421 ms
|
ClickBench: Total hot run time: 32.26 s
|
PR approved by anyone and no changes requested. |
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.
LGTM
PR approved by at least one committer and no changes requested. |
…FE (#40260) The previous implement forgets to build `storageVaultPrivTable` (in-memory) after loading auth information from image, which means the privileges are persisted but unable to use after restarting FE. Note: a new image will be generated after FE restarts or a checkpoint is triggered, the newly generated will be used when FE starts.
The previous implement forgets to build
storageVaultPrivTable
(in-memory) after loading auth information from image, which means the privileges are persisted but unable to use after restarting FE.Note: a new image will be generated after FE restarts or a checkpoint is triggered,
the newly generated will be used when FE starts.