You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d3b60b3
Browse filesBrowse the repository at this point in the historyBrowse files
chenjunwei
authored and
chenjunwei
committed
[fix](be) Preserve the vault SSE flag in storage diagnostics
### What problem does this PR solve?
Related PR: apache#69605
Problem Summary: Migrating the BE storage binding from S3Conf dropped the sse_enabled value carried by ObjectStoreInfoPB. The previous BE included that value in vault creation and error diagnostics. Carry it on ObjStorageConfig, keep the original false default and print it in the storage and flat-source diagnostics. Client construction, caching and the upload path continue to use their existing inputs.
### Release note
BE vault diagnostics retain the sse_enabled value from storage metadata.
### Check List (For Author)
- Test: Built FE and the ASAN BE with Azure enabled. Build hygiene, clang-format 16 and clang-tidy passed. The new test failed on the previous code for both missing log fields and passed after the fix. 242 selected ASAN_UT cases passed, with 34 external-storage cases skipped.
- Behavior changed: No relative to master. The refactored BE reports the vault SSE value again.
- Does this need documentation: No
0 commit comments